This page lists every tool the Data Visions connector offers to customers. Your AI app sees only the tools your role and your connection allow; the rest are hidden rather than offered and refused. For how to connect, see The Data Visions connector (MCP).
How to read the tables
- Changes data? Yes means the tool creates, changes or deletes something. The AI app is told so, and asks you before running it if the app supports that.
- Who can use it:
- Any user: anyone in the workspace who has connected.
- Workspace Admin: Workspace Admins only.
- Needs a permission: anyone whose role holds the permission named.
- Tools that change records also need the workspace's AI connectors setting at Read and make changes, and Read and make changes chosen when connecting. Tools that build or deploy modules need Read and make changes chosen when connecting. See Security: AI connectors.
Workspace and sign-in
| Tool | What it does | Changes data? | Who can use it |
|---|---|---|---|
whoami | Who you are, the workspace this connection works in, your role, your permissions by module, what this connection may do, when its access expires and whether you signed in with two-factor. Says when reconnecting would give the connection more. | No | Any user |
my_tenants | Your workspaces, your type in each, which one the connection is working in now, and invitations waiting for you. | No | Any user |
switch_tenant | Moves this connection to another of your workspaces. Later calls work there, with your permissions there and that workspace's AI connectors setting. | No (it changes the connection, not data) | Any user, in workspaces they belong to |
Module building
All of these follow the module rules: you check out only modules your workspace owns, and deploy only into the workspace you are working in. The connector accepts up to 400 files and about 8 MB per module (2 MB a file); larger modules go through the CLI.
| Tool | What it does | Changes data? | Who can use it |
|---|---|---|---|
sdk_doc | Reads the Module SDK: the workflow (SKILL.md), the onboarding coach (skills/starting-a-module/SKILL.md), how-to skills, references and the example module. With no path, returns the index. Long files come in pages. | No | Workspace Admin |
platform_features | What a module may use from the platform (storage, AI, data, forms, charts, events, schedules and more), from the SDK's references/platform-features.md. Anything not listed isn't available to modules. | No | Workspace Admin |
list_modules | Modules your workspace can see: its own, ones shared with it, and Marketplace modules from other publishers. Filter by mine, subscribed or available. Every module code listed is taken. | No | Any user |
module_versions | One module's versions, which one is installed, and the workspace's install, update and rollback history for it. | No | Any user |
module_logs | The latest log lines from the workspace's module runtime, optionally only lines that mention one module. | No | Workspace Admin |
validate_module | Runs the quick checks on a module's files without deploying. Returns findings (what, why, how to fix) and recommendations to put to you as questions. | No | Workspace Admin |
review_module | Runs the full module check without deploying: the validator, the security scan, vulnerable libraries and an AI code review. Returns what must be fixed. Can take a minute or more. | No | Workspace Admin |
escalate_module_review | Appeals a build the module check blocked, with your reasons, to Data Visions staff, who approve that exact build or reject it with notes. | Yes | Workspace Admin |
checkout_module | Gets the latest code of a module your workspace owns, plus the base a check-in must name, and who else has it checked out. Small modules come back whole; for larger ones, the file list. | No | Workspace Admin |
checkin_module | Sends changed files back as the next revision of the module's draft. Refused if the module moved on since the check-out. Nothing goes live: a Workspace Admin previews and publishes the draft in the Module Builder. | Yes | Workspace Admin |
deploy_module | Checks, uploads and registers a module in your workspace and refreshes it, the same as dv modules deploy. Can subscribe the workspace on the first deploy. The version must go up. Can take a few minutes. | Yes | Workspace Admin |
module_connections | How your workspace's modules connect: each module's services and record sources, what it uses from other modules, its outside APIs, and which workspace integrations (such as Microsoft 365) are connected and granted to which module. | No | Workspace Admin |
See Build a module with a coding agent, start to finish, Publish a module: the module check and Several people changing one module.
Marketplace
| Tool | What it does | Changes data? | Who can use it |
|---|---|---|---|
submit_to_marketplace | Submits the latest deployed version of a module your workspace owns for Marketplace review. It must be marked for the Marketplace and include QA procedures. A refusal lists every blocking finding with its fix. | Yes | Workspace Admin |
marketplace_status | Your workspace's Marketplace submissions: each version's status (in review, listed, rejected, delisted) and the reviewer's notes. | No | Workspace Admin |
creator_sales | For a workspace that publishes Marketplace modules: earnings by month and module, split into your share and Data Visions' share. For one module, which workspaces subscribe (names only) and since when. | No | Workspace Admin |
Data and reports
| Tool | What it does | Changes data? | Who can use it |
|---|---|---|---|
list_datasets | The datasets (published module data) you can report on. With a dataset name, its dimensions, metrics and filters. | No | Needs DASHBOARDS.USE_AGENT or REPORTS.USE_AGENT |
query_dataset | Runs a grouped query on one dataset: dimensions, metrics, filters, sort and a limit (up to 500 rows). | No | Any user; the dataset's own permission applies |
The dashboard and report tools are under Dashboards, reports and websites below.
Module actions
Everything a module's screens can do is also available as an action: one of the module's own routes, with the same permission and rules as in the app.
| Tool | What it does | Changes data? | Who can use it |
|---|---|---|---|
module_actions | Lists the actions of one module that your role allows: name, what it does and whether it changes data. Narrow it with words, or ask for one action's inputs. Actions that need a person's approval in the app are marked as app-only. | No | Any user; your role decides which actions are listed |
run_module_action | Runs one action as you. Actions that change data need the connection to allow changes; a refusal comes back with the module's own reason. | Depends on the action | Any user; the action's own permission applies |
The AI is told to prefer a module's own tool or skill when one fits the job, and to use actions for everything else.
Bridge
| Tool | What it does | Changes data? | Who can use it |
|---|---|---|---|
bridge_computers | Your workspace's PCs running the Data Visions Bridge Harness, as the Bridges page shows them: online state, harness version, who is signed in, and each Bridge Connector with its version, health and settings. | No | Workspace Admin |
set_bridge_connector_settings | Changes settings of a Bridge Connector on one PC. Only the settings the connector declares; the PC applies them within a minute. | Yes | Workspace Admin |
Usage
| Tool | What it does | Changes data? | Who can use it |
|---|---|---|---|
usage_summary | Active users (daily, weekly, monthly), seats, sign-ins, screen views and AI sessions over a window, each compared with the window before. | No | Workspace Admin |
usage_users | Per person: last sign-in, last active, active days, screen views, AI sessions and top modules. Can list only people inactive for a number of days. | No | Workspace Admin |
usage_modules | Per subscribed module: active users, adoption, screen views and requests. Unused modules show with zeros. | No | Workspace Admin |
usage_actions | Which actions people use most: screens and requests, tools run by the in-app assistant and tools run by connected AI apps, with uses, people, errors and average time. | No | Workspace Admin |
Skills and the CLI
| Tool | What it does | Changes data? | Who can use it |
|---|---|---|---|
module_skills | The skills you can use: workspace-assistant, the dashboard and report skills, and the skills of the modules you can open. | No | Any user |
module_skill | Reads one skill's full instructions, or one of its reference files. | No | Any user |
cli_setup | Per-user steps to install, check, sign in to and update the Data Visions CLI on Windows, macOS or Linux, with a download link made for you that works for 15 minutes. | No | Any user |
Dashboards, reports and websites
These platform tools appear next to module tools, with [DASHBOARDS], [REPORTS] or [SITES] at the start of their description. Your role's permissions decide which ones you get.
Dashboards. Changes need the workspace at Read and make changes.
| Tool | What it does | Changes data? | Who can use it |
|---|---|---|---|
describe_dataset | A dataset's full schema: dimensions, metrics, filters and joins. | No | Needs DASHBOARDS.USE_AGENT |
list_filter_values | The values a dataset filter can take. | No | The dataset's own permission |
generate_chart | Builds a chart from a query, ready to show or save. | No | Needs DASHBOARDS.USE_AGENT |
list_user_dashboards, list_tabs, list_components, get_component_detail, get_tab_global_filters | Your dashboards, their tabs, the charts on a tab, one chart's detail and a tab's filter bar. | No | Needs DASHBOARDS.READ_OWN |
list_share_people, get_dashboard_shares | Who a dashboard can be shared with, and who it is shared with now. | No | Needs DASHBOARDS.READ_OWN |
create_dashboard | Creates a dashboard you own. | Yes | Needs DASHBOARDS.CREATE |
create_tab, update_tab, delete_tab | Adds, changes or permanently deletes a tab. | Yes | Needs DASHBOARDS.EDIT_OWN |
save_chart_to_dashboard, update_component, remove_component | Saves, changes or permanently removes a chart. | Yes | Needs DASHBOARDS.EDIT_OWN |
update_dashboard, delete_dashboard | Changes or permanently deletes a dashboard. | Yes | Needs DASHBOARDS.EDIT_OWN |
set_dashboard_shares, transfer_dashboard | Changes who can view a dashboard, or hands it to another person. | Yes | Needs DASHBOARDS.READ_OWN |
Reports. Saving, changing, sharing and deleting your own reports needs only reading, because a report is a view of data each reader may already see.
| Tool | What it does | Changes data? | Who can use it |
|---|---|---|---|
list_reports, get_report | The reports you can see, and one report's full design. | No | Needs REPORTS.READ_OWN |
module_reports | A module's Reports tab as you see it: its ready-made templates and saved reports. | No | Needs REPORTS.READ_OWN |
list_report_templates | Ready-made reports from the modules whose Reports tab you can open. | No | Needs REPORTS.READ_OWN |
render_report | A saved report, with its data fetched now as you. | No | Needs REPORTS.READ_OWN |
preview_report | Tries a report design without saving it. | No | Needs REPORTS.USE_AGENT |
create_report, create_report_from_template | Saves a new report, from scratch or from a template. | Yes (your own reports) | Needs REPORTS.CREATE |
update_report, delete_report | Changes or deletes a report (owner or Workspace Admin for delete). | Yes (your own reports) | Needs REPORTS.EDIT_OWN |
share_report | Shares a report to view with people or the whole workspace. | Yes (your own reports) | Needs REPORTS.READ_OWN |
Websites. Changes need Read and make changes chosen when connecting; the workspace's records setting doesn't apply. Uploading website code is done with the CLI.
| Tool | What it does | Changes data? | Who can use it |
|---|---|---|---|
sites_list, site_detail | The workspace's websites, and one site's versions and domains. | No | Needs SITES.READ |
site_versions_refresh | Checks a version that is still building. | No | Needs SITES.READ |
site_source_files, site_source_read | Lists and reads the files of a website version. | No | Needs SITES.MANAGE |
site_edit | Saves changes as a new website version. | Yes | Needs SITES.MANAGE |
site_publish | Puts a version live; publishing an earlier version rolls back. | Yes | Needs SITES.PUBLISH |
site_domain_add, site_domain_verify | Attaches a domain and checks its DNS. | Yes | Needs SITES.MANAGE |
site_route_add, site_route_remove | Serves a path of one site's domain with another of your sites, or stops it. | Yes | Needs SITES.MANAGE |
Module tools
Besides the built-in tools, the connector offers each subscribed module's own tools: the same ones the module's in-app AI assistant uses. A module developer writes them as @platform_tool functions; see Agent tools, skills and scripts.
- How to spot them. Each one's description starts with the module code in brackets, for example
[TIME_TRACKING] .... The AI app shows the title as MODULE_CODE: tool name. - "(changes data)". A tool that creates, changes or deletes records has (changes data) after the module code, and is marked so the AI app asks you before each call. These appear only when the workspace is at Read and make changes and you chose Read and make changes when connecting. Tools that only read appear on any connection that allows reading data.
- Only what your role allows. A module tool is listed only if your role holds its permission. Ask your Workspace Admin to change your role if a tool you need is missing.
- Not every tool is offered. Tools that need a person's approval in the app, and tools that run on a PC through the Bridge, aren't offered to connected AI apps. Finish those in Data Visions.
- Results are capped at 200,000 characters. If a tool returns more, the AI is asked to narrow the request.
- Built-in names win. A module tool never replaces a built-in tool of the same name.
Each module can also ship skills that tell the AI how to use its tools; the AI reads them with module_skills and module_skill.
Good to know
- A tool you expected isn't listed? Your role, the workspace's AI connectors setting or your connection choice rules it out. Ask the AI to run
whoamito see which. - Every call is in the audit log, with the tool, the outcome and a summary of the inputs, never file contents.
- Bulk changes preview first. Module tools that change many records return a preview; the AI applies it only after your yes.
- The CLI does the same module work from a terminal. See CLI command reference.
- Tool names can grow. New tools appear in your AI app as the platform adds them; this page lists those available today.