Remove a widget from the grid
AI agents call gridstack_remove_widget to permanently remove resources in GridStack MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a widget from the grid is a destructive operation: the widget is deleted from the layout and cannot be recovered without re-adding it. This is not a simple write/update but an irreversible removal, placing it in the Destructive category. Severity is medium because the blast radius is limited to a single widget on a dashboard layout, not system-wide data loss.
From the tool's definition 'Remove a widget from the grid' — removal of a widget is an irreversible deletion of that element from the grid layout
Attacks that exploit this kind of access
Remove a widget from the grid. It is categorised as a Destructive tool in the GridStack MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GridStack MCP Server MCP server in PolicyLayer and add a rule for gridstack_remove_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 GridStack MCP Server. Nothing to install.
gridstack_remove_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 gridstack_remove_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 gridstack_remove_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.
gridstack_remove_widget is provided by the GridStack MCP Server MCP server (raghavsharma-simpplr/gridstack-mcp-server). 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 →