# run_workflow

使用指定工作流执行任务

Agent View of the PolicyLayer registry record for `run_workflow`. HTML page: https://policylayer.com/tools/7836246-claude-team-mcp/run-workflow

## Facts

- Tool: `run_workflow`
- Server: Claude Team MCP (`7836246/claude-team-mcp`) — https://policylayer.com/tools/7836246-claude-team-mcp.md
- Homepage: https://github.com/7836246/claude-team-mcp
- Risk category: Execute (High risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "run_workflow",
    "arguments": {}
  }
}
```

## 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 own definition: "Tool executes a workflow with unspecified arguments ('使用指定工作流执行任务' translates to 'execute task using specified workflow')."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Claude Team MCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_workflow": {
      "limits": [
        {
          "counter": "run_workflow_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Claude Team MCP (17)

- `fix_bug` — Execute — https://policylayer.com/tools/7836246-claude-team-mcp/fix-bug.md
- `team_work` — Execute — https://policylayer.com/tools/7836246-claude-team-mcp/team-work.md
- `analyze_project_structure` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/analyze-project-structure.md
- `ask_expert` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/ask-expert.md
- `code_review` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/code-review.md
- `cost_estimate` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/cost-estimate.md
- `explain_plan` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/explain-plan.md
- `history_context` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/history-context.md
- `history_get` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/history-get.md
- `history_list` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/history-list.md
- `history_search` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/history-search.md
- `list_workflows` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/list-workflows.md
- `read_project_files` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/read-project-files.md
- `suggest_workflow` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/suggest-workflow.md
- `team_dashboard` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/team-dashboard.md
- `usage_stats` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/usage-stats.md
- `generate_commit_message` — Write — https://policylayer.com/tools/7836246-claude-team-mcp/generate-commit-message.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=7836246-claude-team-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/7836246-claude-team-mcp