AI agents call get_grid_state to retrieve information from Ogrid without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
gridId | string | Yes | Grid ID as registered by connectGridToBridge() |
maxRows | integer | — | Max rows to include when includeData=true (default: 20) |
includeData | boolean | — | Whether to include the full row data (default: false - shows only summary) |
Parameters from the server's own tool schema.
This tool performs a read-only query of OGrid state. It retrieves and reports on existing configuration and display parameters without creating, modifying, deleting, executing code, or performing financial operations. The action is purely informational with no side effects.
From the tool's definition Tool description explicitly states it 'Get[s] the current state' of an OGrid instance, retrieving information about 'displayed rows, columns, sort, filters, pagination, and selection' with no mention of modification or side effects.
Attacks that exploit this kind of access
Get the current state of a connected OGrid instance: displayed rows, columns, sort, filters, pagination, and selection. It is categorised as a Read tool in the Ogrid MCP Server, which means it retrieves data without modifying state.
get_grid_state accepts 3 parameters: gridId, maxRows, includeData. Required: gridId. The full parameter table on this page comes from the server's own tool schema.
Register the Ogrid MCP server in PolicyLayer and add a rule for get_grid_state: 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 Ogrid. Nothing to install.
get_grid_state 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 get_grid_state 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 get_grid_state. 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.
get_grid_state is provided by the Ogrid MCP server (@alaarab/ogrid-mcp). 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 →