运行综合。自动执行 reset_run → launch_runs → wait_on_run。
AI agents invoke run_synthesis to trigger actions in 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.
This tool triggers an automated synthesis run in Xilinx Vivado, which executes design compilation and optimization logic. While not destructive (synthesis results can be regenerated), it is an Execute-category tool because it launches a complex computational process whose outcomes depend on the input design and cannot be trivially rolled back without re-running.
From the tool's definition Tool description states it performs synthesis workflow: 'reset_run → launch_runs → wait_on_run'. These are direct operations that execute FPGA design synthesis, a computational process with external effects on the project state and generated artifacts.
Documented attack patterns abuse exactly the kind of access run_synthesis gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vivado, and nothing reaches the server without passing your rules. This is the rule we recommend for run_synthesis:
{
"version": "1",
"default": "deny",
"tools": {
"run_synthesis": {
"limits": [
{
"counter": "run_synthesis_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_synthesis 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.
Free to start. No card required.
运行综合。自动执行 reset_run → launch_runs → wait_on_run。. It is categorised as a Execute tool in the Vivado MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vivado MCP server in PolicyLayer and add a rule for run_synthesis: 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. Nothing to install.
run_synthesis 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 run_synthesis 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 run_synthesis. 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.
run_synthesis is provided by the Vivado MCP server (mapleleavessssssss-wq/vivado-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vivado, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
27 Vivado tools catalogued and risk-classified — across an index of 43,000+ MCP servers.