Parses a text command against PYMOL_COMMANDS, builds PyMOL code,
AI agents invoke parse_and_execute to trigger actions in PyMOL-MCP-Vis. 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 dynamically constructed PyMOL commands based on parsed user input. While PyMOL is a specialized molecular visualization tool with limited destructive capacity compared to a general-purpose shell, it can still execute arbitrary operations within the PyMOL ecosystem—loading molecules, modifying structures, running scripts, and potentially exporting data.
From the tool's definition Tool description states it 'Parses a text command' and 'builds PyMOL code', indicating code generation and execution.
Attacks that exploit this kind of access
Parses a text command against PYMOL_COMMANDS, builds PyMOL code,. It is categorised as a Execute tool in the PyMOL-MCP-Vis MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PyMOL-MCP-Vis MCP server in PolicyLayer and add a rule for parse_and_execute: 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 PyMOL-MCP-Vis. Nothing to install.
parse_and_execute 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 parse_and_execute 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 parse_and_execute. 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.
parse_and_execute is provided by the PyMOL-MCP-Vis MCP server (ryannmperez/pymol-mcp-vis). 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 →