reject_workflow · MCP for Vivado MCP: Risk & Policy

WHAT IT DOES

What reject_workflow does on MCP for Vivado

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

WHY IT NEEDS A POLICY

Why reject_workflow needs a policy

Rejecting a workflow modifies its status from pending/submitted to rejected, which is a reversible state change (workflows can typically be resubmitted or recreated). This is a Write operation rather than Destructive because the workflow data itself is not deleted, only its status is updated.

From the tool's definition Tool name 'reject_workflow' and description 'Reject a workflow' indicate modification of workflow state. Related tools include 'cancel_workflow', 'confirm_workflow', and 'create_workflow', establishing this as a workflow management operation that changes…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reject_workflow Rate-limited

reject_workflow 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": {
    "reject_workflow": {
      "limits": [
        {
          "counter": "reject_workflow_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 MCP for Vivado, so you can run agents against it safely.

FAQ

Questions about reject_workflow

What does the reject_workflow tool do? +

Reject a workflow. It is categorised as a Write tool in the MCP for Vivado MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on reject_workflow? +

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

What risk level is reject_workflow? +

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

Can I rate-limit reject_workflow? +

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

How do I block reject_workflow completely? +

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

What MCP server provides reject_workflow? +

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