update_query_parameter_type · Redash MCP Server MCP

WHAT IT DOES

What update_query_parameter_type does on Redash MCP Server

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

This tool performs a write operation that alters query parameter configuration. While reversible (parameters can be re-updated), it could affect query behavior and potentially break dependent dashboards or visualizations if the type change causes validation failures.

From the tool's definition 'Update the type of a specific parameter' indicates modification of query configuration. The tool modifies an existing parameter's type attribute, which is a reversible change to query metadata.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_query_parameter_type Rate-limited

update_query_parameter_type 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_parameter_type": {
      "limits": [
        {
          "counter": "update_query_parameter_type_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_parameter_type

What does the update_query_parameter_type tool do? +

Update the type of a specific parameter in 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 update_query_parameter_type? +

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

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

Can I rate-limit update_query_parameter_type? +

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

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

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