managed_agent_events

Fetch the full server-persisted event log of a managed cloud-agent session (user turns, agent thinking, tool_use, tool_result, status) — the transcript/artifact view, the CLOUD counterpart of wasm_agent_files. Use when native Read is wrong because the work happened in Anthropic\

SERVERClaude Flow SOURCEclaude-flow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What managed_agent_events does on Claude Flow

AI agents call managed_agent_events to retrieve information from Claude Flow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why managed_agent_events is rated Low

This tool retrieves and queries historical event data from a managed cloud-agent session without modifying, deleting, or executing operations. However, severity is elevated to 'medium' rather than 'low' because the event log may contain sensitive information about agent reasoning, tool usage, and user turns in a multi-tenant cloud environment.

From the tool's definition Tool description states 'Fetch the full server-persisted event log' and explicitly frames itself as retrieving/viewing a 'transcript/artifact'.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs managed_agent_events 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 managed_agent_events, this is the rule to start with:

managed_agent_events Allowed

managed_agent_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "managed_agent_events": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about managed_agent_events

What does the managed_agent_events tool do? +

How do I enforce a policy on managed_agent_events? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for managed_agent_events: 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 managed_agent_events? +

managed_agent_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit managed_agent_events? +

Yes. Add a rate_limit block to the managed_agent_events 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 managed_agent_events completely? +

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

managed_agent_events 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 496 Claude Flow tools →

Across the catalogue

get_agent on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →