agent_execute

A execute tool on the Claude Flow MCP server.

SERVERClaude Flow SOURCEclaude-flow

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/agent-execute.md

WHAT IT DOES

What agent_execute does on Claude Flow

AI agents invoke agent_execute to trigger actions in Claude Flow. 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.

RISK

Why agent_execute is rated High

Execute-named tools typically run code or trigger operations with unpredictable external effects.

From the tool's definition uninformative description; tool name 'agent_execute' suggests code execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs agent_execute safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agent_execute, this is the rule to start with:

agent_execute Rate-limited

agent_execute 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "agent_execute": {
      "limits": [
        {
          "counter": "agent_execute_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every agent_execute call is checked against it from then on.

FAQ

Questions about agent_execute

What does the agent_execute tool do? +

agent_execute is a execute tool on the Claude Flow MCP server. It is categorised as a Execute tool in the Claude Flow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on agent_execute? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for agent_execute: 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 Flow. Nothing to install.

What risk level is agent_execute? +

agent_execute is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit agent_execute? +

Yes. Add a rate_limit block to the agent_execute 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.

How do I block agent_execute completely? +

Set action: deny in the PolicyLayer policy for agent_execute. 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.

What MCP server provides agent_execute? +

agent_execute is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 546 Claude Flow tools → High-risk tools on this server →

Across the catalogue

claude_execute on Claude Bridge →execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →