Get current float state
AI agents call gridstack_get_float to retrieve information from GridStack MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves state information (float configuration) from the GridStack layout without making any changes to the layout, data, or system. It has no side effects and falls squarely into the Read category as a getter/query operation. The low severity reflects that reading layout state poses minimal risk to the application.
From the tool's definition Tool name 'gridstack_get_float' and description 'Get current float state' indicate a read-only query operation that retrieves the current floating state of grid elements without modification.
Attacks that exploit this kind of access
Get current float state. It is categorised as a Read tool in the GridStack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GridStack MCP Server MCP server in PolicyLayer and add a rule for gridstack_get_float: 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_get_float is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gridstack_get_float 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_get_float. 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_get_float 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 →