Query stored entities with filters.
AI agents call state_query to retrieve information from Onboarded 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 or queries data stored in entity memory with optional filtering, producing no side effects. It matches the Read category definition of retrieving data without modification. Severity is low because querying stored state poses minimal risk—the worst case is information disclosure of already-persisted data, which is far less damaging than write, execute, or destructive operations.
From the tool's definition Tool name 'state_query' and description 'Query stored entities with filters' indicate data retrieval without modification. The verb 'query' combined with 'filters' is a classic read operation pattern.
Attacks that exploit this kind of access
Query stored entities with filters. It is categorised as a Read tool in the Onboarded MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Onboarded MCP Server MCP server in PolicyLayer and add a rule for state_query: 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 Onboarded MCP Server. Nothing to install.
state_query 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 state_query 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 state_query. 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.
state_query is provided by the Onboarded MCP Server MCP server (onboardedinc/onboarded-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 →