Delete a widget from a dashboard
AI agents call delete_widget to permanently remove resources in Redash MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The delete_widget tool performs an irreversible destruction of data—removing a widget from a dashboard cannot be undone through normal operational means. While the scope (a single widget) is narrower than deleting an entire dashboard, it still constitutes destructive action on configured dashboard state.
From the tool's definition Tool name explicitly uses "delete" and description states it removes ("Delete a widget from a dashboard"). The action irreversibly removes a dashboard component.
Attacks that exploit this kind of access
Delete a widget from a dashboard. It is categorised as a Destructive tool in the Redash MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Redash MCP Server MCP server in PolicyLayer and add a rule for delete_widget: 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.
delete_widget is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_widget 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 delete_widget. 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.
delete_widget 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 →