Remove all widgets from the grid
AI agents call gridstack_remove_all 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.
This tool removes all widgets at once, which is a bulk destructive action that cannot be easily undone without external state recovery. While the grid itself remains, all configured widget state is lost. The 'remove all' pattern indicates a high-severity destructive operation that an agent could invoke accidentally or maliciously, destroying a user's entire dashboard configuration.
From the tool's definition Tool name is 'gridstack_remove_all' and description states 'Remove all widgets from the grid' — this irreversibly deletes all widgets from a dashboard layout in a single operation.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Remove all widgets 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_all: 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_all 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_all 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_all. 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_all 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 →