run_simulation · MCP for Vivado MCP: Risk & Policy

WHAT IT DOES

What run_simulation does on MCP for Vivado

AI agents invoke run_simulation to trigger actions in MCP for Vivado. 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.

WHY IT NEEDS A POLICY

Why run_simulation needs a policy

This tool triggers execution of simulation workflows, which are computational operations external to the agent. While simulations are typically non-destructive and generate temporary outputs, the effects are determined by the arguments passed (design inputs, testbench scenarios) and could consume significant resources or produce incorrect timing/functional validation results if misused.

From the tool's definition Tool name 'run_simulation' with description 'Run a simulation workflow intent' indicates execution of a simulation process.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_simulation Rate-limited

run_simulation stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_simulation": {
      "limits": [
        {
          "counter": "run_simulation_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP for Vivado, so you can run agents against it safely.

FAQ

Questions about run_simulation

What does the run_simulation tool do? +

Run a simulation workflow intent. It is categorised as a Execute tool in the MCP for Vivado MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_simulation? +

Register the MCP for Vivado MCP server in PolicyLayer and add a rule for run_simulation: 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 MCP for Vivado. Nothing to install.

What risk level is run_simulation? +

run_simulation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_simulation? +

Yes. Add a rate_limit block to the run_simulation 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.

How do I block run_simulation completely? +

Set action: deny in the PolicyLayer policy for run_simulation. 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.

What MCP server provides run_simulation? +

run_simulation is provided by the MCP for Vivado MCP server (lzw12123/mcp-for-vivado). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.