AI agents call get_status to retrieve information from Fairchem without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries the current state of a running simulation and returns monitoring data. This is a read-only operation that retrieves information without side effects, triggering any computations, or modifying state. Low severity because misuse merely returns incorrect or stale status information, not damaging outcomes.
From the tool's definition Tool name 'get_status' and description indicating it retrieves 'a live snapshot of a job: status, step, energy, max_force' — these are query/retrieval operations with no modification or execution of underlying simulations.
Attacks that exploit this kind of access
Get a live snapshot of a job: status, step, energy, max_force, and a. It is categorised as a Read tool in the Fairchem MCP Server, which means it retrieves data without modifying state.
Register the Fairchem MCP server in PolicyLayer and add a rule for get_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 Fairchem. Nothing to install.
get_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 get_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 get_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.
get_status is provided by the Fairchem MCP server (jkitchin/fairchem-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 →