add_query_parameter · Redash MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_query_parameter does on Redash MCP Server

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

This tool creates or modifies query parameters within Redash queries. While parameters themselves are configuration metadata (not destructive data deletion), adding parameters to queries can alter query behavior and results. This is reversible—parameters can be removed or changed—making it a Write operation rather than Execute or Destructive.

From the tool's definition Tool name 'add_query_parameter' and description 'Add a new parameter to a Redash query' indicate creation/modification of query parameters, which is a reversible data modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_query_parameter Rate-limited

add_query_parameter 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": {
    "add_query_parameter": {
      "limits": [
        {
          "counter": "add_query_parameter_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 add_query_parameter

What does the add_query_parameter tool do? +

Add a new parameter to a Redash query. 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 add_query_parameter? +

Register the Redash MCP Server MCP server in PolicyLayer and add a rule for add_query_parameter: 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 add_query_parameter? +

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

Can I rate-limit add_query_parameter? +

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

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

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