Prepare input files for ABACUS DFPT phonon calculation.
AI agents use run_phonon_preparation to create or update resources in Abacus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Abacus environment.
This tool creates/writes input files for a phonon calculation. It does not execute the calculation itself, merely prepares the necessary files. This is a Write operation (creating new files on the filesystem). Severity is medium because misuse could overwrite existing calculation inputs or produce incorrect scientific configurations, but it is reversible.
From the tool's definition Prepare input files for ABACUS DFPT phonon calculation
Documented attack patterns abuse exactly the kind of access run_phonon_preparation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Abacus, and nothing reaches the server without passing your rules. This is the rule we recommend for run_phonon_preparation:
{
"version": "1",
"default": "deny",
"tools": {
"run_phonon_preparation": {
"limits": [
{
"counter": "run_phonon_preparation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} run_phonon_preparation stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Prepare input files for ABACUS DFPT phonon calculation. It is categorised as a Write tool in the Abacus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Abacus MCP server in PolicyLayer and add a rule for run_phonon_preparation: 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 Abacus. Nothing to install.
run_phonon_preparation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the run_phonon_preparation 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 run_phonon_preparation. 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.
run_phonon_preparation is provided by the Abacus MCP server (phelanshao/abacus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Abacus, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 Abacus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.