AI agents call lexq_simulation_status to retrieve information from LexQ without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the current state and outcomes of simulations that have already been run. It is a read-only operation that queries existing data (simulation status and results) with no side effects, no execution of code, and no data modification. The polling mechanism is passive monitoring, not an action that triggers changes.
From the tool's definition Tool name 'lexq_simulation_status' and description 'Get simulation status and results. Poll until status is COMPLETED or FAILED' indicate a query/polling operation that retrieves status information without modifying or executing anything.
Attacks that exploit this kind of access
Get simulation status and results. Poll until status is COMPLETED or FAILED. It is categorised as a Read tool in the LexQ MCP Server, which means it retrieves data without modifying state.
Register the LexQ MCP server in PolicyLayer and add a rule for lexq_simulation_status: 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 LexQ. Nothing to install.
lexq_simulation_status 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 lexq_simulation_status 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 lexq_simulation_status. 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.
lexq_simulation_status is provided by the LexQ MCP server (lexq-io/lexq-cli). 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 →