AI agents use add_representation to create or update resources in Vmd — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vmd environment.
The tool adds configuration/metadata to an existing molecule (a new representation), which is a reversible modification. It does not delete, execute arbitrary commands, or have financial impact. While VMD2 is scientific software, the blast radius of misuse is limited to the visualization layer—a user could add unwanted representations, but this is easily undone via delete_representation.
From the tool's definition Tool creates a new visual representation in VMD2 ('Add a new visual representation'). This modifies the state of the molecular visualization without removing or deleting existing data, consistent with reversible Write operations.
Attacks that exploit this kind of access
Add a new visual representation to a molecule WITHOUT removing existing ones. It is categorised as a Write tool in the Vmd MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vmd MCP server in PolicyLayer and add a rule for add_representation: 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.
add_representation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_representation 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 add_representation. 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.
add_representation 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 →