# run_flow

跑一条流程（flow 用 list_flows 里的文件名）。事件会自动投影进群，同时写 AgentBus。

Agent View of the PolicyLayer registry record for `run_flow`. HTML page: https://policylayer.com/tools/a2p2a/run-flow

## Facts

- Tool: `run_flow`
- Server: A2p2a (`tendQQ/a2p2a`) — https://policylayer.com/tools/a2p2a.md
- Homepage: https://github.com/tendQQ/a2p2a
- 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_flow",
    "arguments": {}
  }
}
```

## Why run_flow is rated High

Executes a workflow with automatic side effects including projecting events into group and writing to AgentBus state.

From the tool's own definition: "run_flow, 跑一条流程, 自动投影进群, 写 AgentBus"

## Use case

AI agents invoke run_flow to trigger actions in A2p2a. 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 A2p2a:

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

## Other tools on A2p2a (14)

- `manage` — Execute — https://policylayer.com/tools/a2p2a/manage.md
- `agent_bus_state` — Read — https://policylayer.com/tools/a2p2a/agent-bus-state.md
- `analyze` — Read — https://policylayer.com/tools/a2p2a/analyze.md
- `intervene` — Read — https://policylayer.com/tools/a2p2a/intervene.md
- `list_agents` — Read — https://policylayer.com/tools/a2p2a/list-agents.md
- `list_flows` — Read — https://policylayer.com/tools/a2p2a/list-flows.md
- `list_workspaces` — Read — https://policylayer.com/tools/a2p2a/list-workspaces.md
- `read_group` — Read — https://policylayer.com/tools/a2p2a/read-group.md
- `read_scores` — Read — https://policylayer.com/tools/a2p2a/read-scores.md
- `report_progress` — Read — https://policylayer.com/tools/a2p2a/report-progress.md
- `say_in_group` — Read — https://policylayer.com/tools/a2p2a/say-in-group.md
- `talk_to_secretary` — Read — https://policylayer.com/tools/a2p2a/talk-to-secretary.md
- `post_goal` — Write — https://policylayer.com/tools/a2p2a/post-goal.md
- `register_agent` — Write — https://policylayer.com/tools/a2p2a/register-agent.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=a2p2a · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/a2p2a