archive_query · Dune Analytics MCP Server MCP: Risk & Policy

WHAT IT DOES

What archive_query does on Dune Analytics MCP Server

AI agents use archive_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 archive_query needs a policy

The action moves a query to an archived state rather than permanently destroying it, making it a Write operation (reversible modification). Severity is medium because an agent could archive queries belonging to other users or important analyses, disrupting workflow, but the action is reversible (queries can typically be restored from archives).

From the tool's definition Tool description states 'Move a query to the archive, removing it from active workspace.' This is a reversible state change that modifies query visibility/organization without permanently deleting data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

archive_query Rate-limited

archive_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": {
    "archive_query": {
      "limits": [
        {
          "counter": "archive_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 archive_query

What does the archive_query tool do? +

Move a query to the archive, removing it from active workspace. 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 archive_query? +

Register the Dune Analytics MCP Server MCP server in PolicyLayer and add a rule for archive_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 archive_query? +

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

Can I rate-limit archive_query? +

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

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

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