managed_agent_status

Get the lifecycle state of a managed cloud-agent session: idle/running/error, title, last error. Use when native conversation memory is wrong because you need the cloud session\

Server Claude Flow claude-flow
Category Read
Risk class Low
Parameters 00 required

What managed_agent_status does on Claude Flow

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

Why managed_agent_status needs a policy

This tool retrieves status information about a managed agent session without modifying state, triggering actions, or affecting external systems. It is a pure query operation with negligible blast radius if misused by an AI agent.

From the tool's definition Tool description explicitly states 'Get the lifecycle state' and lists read-only outputs: idle/running/error, title, last error. No mutations, side effects, or external operations.

Questions about managed_agent_status

What does the managed_agent_status tool do? +

Get the lifecycle state of a managed cloud-agent session: idle/running/error, title, last error. Use when native conversation memory is wrong because you need the cloud session\. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on managed_agent_status? +

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

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

Can I rate-limit managed_agent_status? +

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

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

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.