vivado_generate_test_plan · Vivado Mcp Agent MCP

WHAT IT DOES

What vivado_generate_test_plan does on Vivado Mcp Agent

AI agents use vivado_generate_test_plan to create or update resources in Vivado Mcp Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vivado Mcp Agent environment.

WHY IT NEEDS A POLICY

Why vivado_generate_test_plan needs a policy

This tool creates test plan documents or specifications in a reversible manner—test plans can be modified, discarded, or regenerated without permanent consequences. It does not execute simulations or implement designs (those are separate tools like vivado_build_bitstream), so it is Write rather than Execute. The impact is limited to planning artifacts, making severity low.

From the tool's definition Tool generates test plans (directed, reset, corner, protocol, random, assertion, scoreboard, coverage). The description explicitly uses 'generate,' indicating creation of new data/artifacts.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vivado_generate_test_plan Rate-limited

vivado_generate_test_plan stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vivado_generate_test_plan": {
      "limits": [
        {
          "counter": "vivado_generate_test_plan_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about vivado_generate_test_plan

What does the vivado_generate_test_plan tool do? +

Generate directed, reset, corner, protocol, random, assertion, scoreboard, and coverage plan. It is categorised as a Write tool in the Vivado Mcp Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on vivado_generate_test_plan? +

Register the Vivado Mcp Agent MCP server in PolicyLayer and add a rule for vivado_generate_test_plan: 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.

What risk level is vivado_generate_test_plan? +

vivado_generate_test_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit vivado_generate_test_plan? +

Yes. Add a rate_limit block to the vivado_generate_test_plan 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 vivado_generate_test_plan completely? +

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

vivado_generate_test_plan 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.