Update a workflow
AI agents use update_workflow to create or update resources in Prowpt MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Prowpt MCP Server environment.
The tool modifies workflow configuration/data on the Prowpt.ai platform, which constitutes a Write action. It is reversible (unlike Destructive), does not execute arbitrary code (unlike Execute), and carries medium severity due to potential impact on application logic if workflows are modified incorrectly, but the blast radius is limited to workflow configuration rather than critical infrastructure or data deletion.
From the tool's definition Tool name 'update_workflow' and description 'Update a workflow' indicate modification of existing workflow data. This is a reversible change operation.
Attacks that exploit this kind of access
Update a workflow. It is categorised as a Write tool in the Prowpt MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Prowpt MCP Server MCP server in PolicyLayer and add a rule for update_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 Prowpt MCP Server. Nothing to install.
update_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 update_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 update_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.
update_workflow is provided by the Prowpt MCP Server MCP server (prowptai/prowpt-mcp-server). 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 →