AI agents invoke start_elastic_scan to trigger actions in Fairchem. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
An elastic scan is a scientific computation that explores energy surfaces across structural deformations. This triggers external operations (molecular dynamics/DFT simulations) whose effects depend on input parameters and cannot be easily interrupted mid-execution.
From the tool's definition Tool name 'start_elastic_scan' combined with server description stating it 'allows LLM agents to load a model once and steer relaxations, MD, NEB, phonons, and minima searches mid-flight' indicates this initiates computational simulations.
Attacks that exploit this kind of access
start_elastic_scan. It is categorised as a Execute tool in the Fairchem MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Fairchem MCP server in PolicyLayer and add a rule for start_elastic_scan: 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.
start_elastic_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_elastic_scan 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 start_elastic_scan. 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.
start_elastic_scan 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 →