Update an existing visualization in Redash
AI agents use update_visualization 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.
This tool modifies visualization configurations reversibly within Redash. Updates can be undone by subsequent changes, so it does not qualify as Destructive. It does not execute arbitrary code (Execute category), nor does it move money (Financial).
From the tool's definition Tool name is 'update_visualization' and description states 'Update an existing visualization in Redash'. The verb 'update' indicates modification of existing data without deletion.
Attacks that exploit this kind of access
Update an existing visualization 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.
Register the Redash MCP Server MCP server in PolicyLayer and add a rule for update_visualization: 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.
update_visualization is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_visualization 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.
Set action: deny in the PolicyLayer policy for update_visualization. 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.
update_visualization 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →