AI agents invoke run_workflow to trigger actions in Unstructured API MCP Server. 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 execution of an external workflow whose effects depend on the workflow's configuration and arguments (which workflow, what data it processes, where outputs are sent). While not inherently destructive, the outcome is contingent on workflow definition and cannot be predicted from the tool call alone.
From the tool's definition Tool name is 'run_workflow' and description states 'Run a specific workflow.' The verb 'run' indicates execution of a defined workflow process.
Documented attack patterns abuse exactly the kind of access run_workflow gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unstructured API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_workflow:
{
"version": "1",
"default": "deny",
"tools": {
"run_workflow": {
"limits": [
{
"counter": "run_workflow_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_workflow 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.
Run a specific workflow. It is categorised as a Execute tool in the Unstructured API MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Unstructured API MCP Server MCP server in PolicyLayer and add a rule for run_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 Unstructured API MCP Server. Nothing to install.
run_workflow 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_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 run_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.
run_workflow is provided by the Unstructured API MCP Server MCP server (unstructured-io/uns-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Unstructured API MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 Unstructured API MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.