Cancel a workflow.
AI agents call cancel_workflow to permanently remove resources in MCP for Vivado — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a running Vivado workflow (synthesis, implementation, timing analysis, etc.) irreversibly stops the process. Any intermediate results or progress may be lost and the workflow would need to be restarted from scratch. This is a non-recoverable termination of an active operation, placing it in the Destructive category with high severity given the potential loss of long-running hardware design computation.
From the tool's definition Cancel a workflow — terminating an in-progress workflow is an irreversible action that aborts synthesis, implementation, or other hardware design processes that cannot be resumed from the same point.
Attacks that exploit this kind of access
Cancel a workflow. It is categorised as a Destructive tool in the MCP for Vivado MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP for Vivado MCP server in PolicyLayer and add a rule for cancel_workflow: 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.
cancel_workflow is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_workflow 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 cancel_workflow. 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.
cancel_workflow 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.
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 →