AI agents invoke execute_tcl to trigger actions in Vmd. 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 allows execution of arbitrary Tcl commands within VMD's runtime environment. While the server context is molecular dynamics analysis, the ability to execute raw Tcl grants the AI agent full programmatic control over VMD, including potential system-level operations. This is functionally equivalent to a shell execution tool.
From the tool's definition Tool name 'execute_tcl' and description 'Send a raw Tcl command directly to VMD' indicate arbitrary code execution capability. Tcl is a scripting language that can invoke system calls, modify molecular structures, delete data, and trigger external operations.
Attacks that exploit this kind of access
Send a raw Tcl command directly to VMD. It is categorised as a Execute tool in the Vmd MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vmd MCP server in PolicyLayer and add a rule for execute_tcl: 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 Vmd. Nothing to install.
execute_tcl 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 execute_tcl 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 execute_tcl. 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.
execute_tcl is provided by the Vmd MCP server (omararias-gaguancela/vmd-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 →