Update cell height
AI agents use gridstack_cell_height 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 modifies grid layout configuration (cell height) in a reversible manner. It creates or updates visual layout data without deleting information or executing arbitrary code. The change is non-destructive and can be undone by setting a different height value. This is a typical Write operation on UI component state.
From the tool's definition Tool name 'gridstack_cell_height' combined with description 'Update cell height' indicates a modification operation that changes grid layout properties.
Attacks that exploit this kind of access
Update cell height. 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_cell_height: 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_cell_height 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_cell_height 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_cell_height. 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_cell_height 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 →