Alias for run_optimization tool. Performs geometry optimization.
AI agents invoke optimize_structure 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 executes an external quantum chemistry/materials science calculation (geometry optimization), which involves running compute-intensive simulations. It is not merely reading data nor writing configuration — it actively triggers an optimization run on potentially large computational resources.
From the tool's definition "Performs geometry optimization" — triggers a computational calculation (geometry optimization) via ABACUS; alias for run_optimization tool indicating it runs an external simulation/computation
Documented attack patterns abuse exactly the kind of access optimize_structure 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 optimize_structure:
{
"version": "1",
"default": "deny",
"tools": {
"optimize_structure": {
"limits": [
{
"counter": "optimize_structure_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}optimize_structure 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.
Alias for run_optimization tool. Performs geometry optimization. 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 optimize_structure: 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.
optimize_structure 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 optimize_structure 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 optimize_structure. 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.
optimize_structure 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.