Run energy minimization on a model.
AI agents invoke minimize_energy to trigger actions in ChimeraX MCP Server. 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.
Energy minimization is a computational operation that executes algorithms to optimize molecular geometry. While it modifies structure coordinates, it is reversible (the original structure can be reloaded) and doesn't permanently destroy data. However, it triggers external computational operations whose effects depend on arguments and model state, making it Execute rather than Write.
From the tool's definition Tool performs 'energy minimization' which executes a computational operation on molecular structures. This is an external computational process triggered by the tool that modifies the state of the protein model being analyzed.
Attacks that exploit this kind of access
Run energy minimization on a model. It is categorised as a Execute tool in the ChimeraX MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ChimeraX MCP Server MCP server in PolicyLayer and add a rule for minimize_energy: 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 ChimeraX MCP Server. Nothing to install.
minimize_energy 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 minimize_energy 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 minimize_energy. 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.
minimize_energy is provided by the ChimeraX MCP Server MCP server (mahynotch/chimerax-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 →