run_dashboard_query

Run a scheduled dashboard query immediately instead of waiting for the daily refresh. Writes the result to the app

SERVERDeloc SOURCEdelocdev/deloc-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/deloc-mcp/run-dashboard-query.md

WHAT IT DOES

What run_dashboard_query does on Deloc

AI agents invoke run_dashboard_query to trigger actions in Deloc. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why run_dashboard_query is rated High

This tool triggers execution of a query with observable side effects (writing results to the app), which goes beyond passive data retrieval. While it modifies app state by writing query results, it is not irreversible (results can be re-run or overwritten) and does not delete data, so Execute is more appropriate than Destructive or Write.

From the tool's definition Tool name 'run_dashboard_query' paired with description stating it 'Run[s] a scheduled dashboard query immediately' and 'Writes the result to the app'.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_dashboard_query safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Deloc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_dashboard_query, this is the rule to start with:

run_dashboard_query Rate-limited

run_dashboard_query stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_dashboard_query": {
      "limits": [
        {
          "counter": "run_dashboard_query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Deloc, apply this rule, and every run_dashboard_query call is checked against it from then on.

FAQ

Questions about run_dashboard_query

What does the run_dashboard_query tool do? +

Run a scheduled dashboard query immediately instead of waiting for the daily refresh. Writes the result to the app. It is categorised as a Execute tool in the Deloc MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_dashboard_query? +

Register the Deloc MCP server in PolicyLayer and add a rule for run_dashboard_query: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Deloc. Nothing to install.

What risk level is run_dashboard_query? +

run_dashboard_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_dashboard_query? +

Yes. Add a rate_limit block to the run_dashboard_query rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block run_dashboard_query completely? +

Set action: deny in the PolicyLayer policy for run_dashboard_query. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides run_dashboard_query? +

run_dashboard_query is provided by the Deloc MCP server (delocdev/deloc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Deloc, and thousands of servers like it.

This server

All 45 Deloc tools → High-risk tools on this server →

Across the catalogue

run on 0sec →aroflo_query_zone on AroFlo MCP →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →