neural_status

Get neural system status Use when nothing native trains on your workflow — Claude Code has no learning loop. Use to train SONA/MoE/EWC patterns from successful task outcomes; query via neural_predict before spawning agents. Off-path for one-shot work.

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

What neural_status does on Claude Flow

AI agents call neural_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 neural_status needs a policy

neural_status is a status/query operation that retrieves information about the neural system's state. It does not create, modify, delete, execute arbitrary operations, or commit financial transactions. The mention of 'training patterns' refers to internal model analysis, not external execution. This is a diagnostic Read tool with minimal blast radius.

From the tool's definition Tool description states 'Get neural system status' and 'query via neural_predict' — both read operations that retrieve system state information without modification.

Questions about neural_status

What does the neural_status tool do? +

Get neural system status Use when nothing native trains on your workflow — Claude Code has no learning loop. Use to train SONA/MoE/EWC patterns from successful task outcomes; query via neural_predict before spawning agents. Off-path for one-shot work. 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 neural_status? +

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

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

Can I rate-limit neural_status? +

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

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

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