AI agents invoke start_phonons 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.
Phonon analysis is a physics simulation that runs code/external operations via FAIRChem/ASE whose effects depend on the structure and parameters passed to it. This is not a read operation (it triggers computation), not write (it doesn't modify data reversibly—it generates new results), and not destructive (nothing is deleted).
From the tool's definition Tool named 'start_phonons' on a server that 'allows LLM agents to...steer relaxations, MD, NEB, phonons, and minima searches mid-flight'.
Attacks that exploit this kind of access
start_phonons. 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_phonons: 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_phonons 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_phonons 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_phonons. 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_phonons 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 →