Run simulation Tcl and save stdout/stderr logs.
AI agents invoke vivado_run_sim to trigger actions in Vivado Mcp Agent. 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 simulation scripts (Tcl code) in Vivado, which is an external operation with side effects that depend on the arguments. While simulation itself is typically non-destructive to the design database, executing arbitrary Tcl code in an FPGA design tool can trigger design modifications, probe placement, waveform generation, or other state changes.
From the tool's definition Tool name "vivado_run_sim" with description "Run simulation Tcl and save stdout/stderr logs" directly executes Tcl code within the Vivado environment.
Attacks that exploit this kind of access
Run simulation Tcl and save stdout/stderr logs. It is categorised as a Execute tool in the Vivado Mcp Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vivado Mcp Agent MCP server in PolicyLayer and add a rule for vivado_run_sim: 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 Vivado Mcp Agent. Nothing to install.
vivado_run_sim 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 vivado_run_sim 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 vivado_run_sim. 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.
vivado_run_sim is provided by the Vivado Mcp Agent MCP server (wangyuxin0707/vivado-mcp-agent). 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 →