update_dashboard_query
Update a scheduled dashboard query: change its SQL, repoint it to a different connection, adjust caps, or enable/disable the schedule. Omitted fields are unchanged.
This record as markdown: /tools/deloc-mcp/update-dashboard-query.md
What update_dashboard_query does on Deloc
AI agents use update_dashboard_query to create or update resources in Deloc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Deloc environment.
Why update_dashboard_query is rated Medium
This tool creates or modifies data reversibly (the hallmark of Write category). Users can update scheduled queries—changing SQL logic, connection targets, caps, or schedule state—but these modifications are not irreversible. The changes can be undone by issuing another update.
From the tool's definition Tool description states it performs update operations: 'change its SQL, repoint it to a different connection, adjust caps, or enable/disable the schedule.' These are reversible modifications to existing resources.
Attacks that exploit this kind of access
The rule that runs update_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 update_dashboard_query, this is the rule to start with:
update_dashboard_query stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Deloc, apply this rule, and every update_dashboard_query call is checked against it from then on.
Questions about update_dashboard_query
Update a scheduled dashboard query: change its SQL, repoint it to a different connection, adjust caps, or enable/disable the schedule. Omitted fields are unchanged. It is categorised as a Write tool in the Deloc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Deloc MCP server in PolicyLayer and add a rule for update_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.
update_dashboard_query is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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.
Set action: deny in the PolicyLayer policy for update_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.
update_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.
More on Deloc, and thousands of servers like it.
This server
Across the catalogue