Destroy the grid instance
AI agents call gridstack_destroy 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.
Destroying a grid instance cannot be undone and eliminates the entire dashboard layout and widget configuration. While the impact is scoped to the grid instance (not data deletion at scale), it represents a significant loss of application state.
From the tool's definition Tool name is 'gridstack_destroy' with description 'Destroy the grid instance' — the verb 'destroy' indicates irreversible removal of a grid instance and its associated state.
Attacks that exploit this kind of access
Destroy the grid instance. 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_destroy: 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_destroy 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_destroy 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_destroy. 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_destroy 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 →