update_query · Redash MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_query does on Redash MCP Server

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

WHY IT NEEDS A POLICY

Why update_query needs a policy

This tool modifies query definitions in Redash but does not delete or execute them. Query updates are reversible (can be reverted or modified again) and have no immediate side effects beyond changing the stored query definition.

From the tool's definition Tool name 'update_query' and description 'Update an existing query in Redash' indicate modification of existing data without deletion.

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 Redash MCP Server, so you can run agents against it safely.

FAQ

Questions about update_query

What does the update_query tool do? +

Update an existing query in Redash. It is categorised as a Write tool in the Redash 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 Redash 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 Redash 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 Redash MCP Server MCP server (jagadeesh52423/redash-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.