Create a workflow record.
AI agents use create_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.
This tool creates a new workflow record, which is a reversible write operation. The context of Vivado hardware design workflows suggests this creates project configuration or process tracking data. While reversible (can be undone by deletion), it modifies the state of the design environment.
From the tool's definition Tool name is 'create_workflow' and description states 'Create a workflow record.' The verb 'create' indicates data creation/modification without deletion.
Attacks that exploit this kind of access
Create a workflow record. 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.
Register the MCP for Vivado MCP server in PolicyLayer and add a rule for create_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.
create_workflow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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 →