This record as markdown: /tools/7836246-claude-team-mcp/run-workflow.md
What run_workflow does on Claude Team MCP
AI agents invoke run_workflow to trigger actions in Claude Team MCP. 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.
Why run_workflow is rated High
run_workflow is an Execute category tool because it executes workflows whose effects depend on the workflow definition and arguments passed to it. While the exact capabilities are unclear due to the vague Chinese description, the context of code development, review, and optimization combined with workflow execution suggests it could trigger code changes, external API calls, or other side effects.
From the tool's definition Tool executes a workflow with unspecified arguments ('使用指定工作流执行任务' translates to 'execute task using specified workflow').
Attacks that exploit this kind of access
The rule that runs run_workflow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Team MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_workflow, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Team MCP, apply this rule, and every run_workflow call is checked against it from then on.
Questions about run_workflow
使用指定工作流执行任务. It is categorised as a Execute tool in the Claude Team MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Team 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 Claude Team MCP. 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 Claude Team MCP server (7836246/claude-team-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Team, and thousands of servers like it.
Across the catalogue