Create a new grid with options and children (static method)
AI agents use gridstack_add_grid to create or update resources in GridStack MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GridStack MCP Server environment.
This tool creates a new grid object/component which modifies the layout state reversibly. It does not execute arbitrary code, delete data, move money, or perform destructive operations. Creation and initialization of UI components falls under Write category. Severity is low because misuse affects only the local dashboard layout and is easily undoable.
From the tool's definition Tool name 'gridstack_add_grid' and description 'Create a new grid' indicate data creation. The tool creates a new grid configuration with options and children, modifying the dashboard layout state.
Attacks that exploit this kind of access
Create a new grid with options and children (static method). It is categorised as a Write tool in the GridStack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GridStack MCP Server MCP server in PolicyLayer and add a rule for gridstack_add_grid: 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_add_grid 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 gridstack_add_grid 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_add_grid. 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_add_grid 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 →