Calculate ABACUS Density of States (DOS).
AI agents invoke calculate_dos to trigger actions in Abacus. 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.
This tool runs a scientific calculation (Density of States) on an external computational backend. It initiates an external operation whose effects depend on arguments (structure, parameters), consistent with Execute. It is not merely reading stored data, but actively running a simulation. Severity is medium as misuse could waste compute resources but has limited broader blast radius.
From the tool's definition 'Calculate ABACUS Density of States (DOS)' — triggers an external quantum chemistry computation using the ABACUS simulation engine
Documented attack patterns abuse exactly the kind of access calculate_dos 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 calculate_dos:
{
"version": "1",
"default": "deny",
"tools": {
"calculate_dos": {
"limits": [
{
"counter": "calculate_dos_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}calculate_dos stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Calculate ABACUS Density of States (DOS). It is categorised as a Execute tool in the Abacus MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Abacus MCP server in PolicyLayer and add a rule for calculate_dos: 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.
calculate_dos 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 calculate_dos 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 calculate_dos. 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.
calculate_dos 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.