update_query · Dune Analytics MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_query does on Dune Analytics MCP Server

AI agents use update_query to create or update resources in Dune Analytics MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dune Analytics MCP Server environment.

WHY IT NEEDS A POLICY

Why update_query needs a policy

The tool name and server context suggest this creates or modifies data reversibly—updating query configurations, metadata, or parameters. The empty description reduces confidence, but the naming pattern and presence of sibling tools (create_query, run_query, run_sql) establish that this operates within data mutation territory rather than pure querying (Read) or irreversible deletion (Destructive).

From the tool's definition Tool name 'update_query' indicates modification of stored query objects. Within Dune Analytics context where sibling tools include 'create_query', 'run_query', and 'run_sql', this tool likely modifies query metadata, parameters, or definitions without…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_query Rate-limited

update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_query": {
      "limits": [
        {
          "counter": "update_query_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Dune Analytics MCP Server, so you can run agents against it safely.

FAQ

Questions about update_query

What does the update_query tool do? +

update_query. It is categorised as a Write tool in the Dune Analytics MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_query? +

Register the Dune Analytics MCP Server MCP server in PolicyLayer and add a rule for update_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 Dune Analytics MCP Server. Nothing to install.

What risk level is update_query? +

update_query is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_query? +

Yes. Add a rate_limit block to the update_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 update_query completely? +

Set action: deny in the PolicyLayer policy for update_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 update_query? +

update_query is provided by the Dune Analytics MCP Server MCP server (sak1337/dune-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.