Health monitoring - check AI orchestration system status, model configuration, and capability testing results. Useful for debugging or verifying system readiness.
AI agents call ai_status to retrieve information from Orchestrator MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves system health and status information without modifying any data or executing external operations. It is purely observational and diagnostic in nature, making it a Read category tool with low severity. The capability testing reference refers to checking results, not executing arbitrary tests that could have side effects.
From the tool's definition Tool description indicates 'check AI orchestration system status, model configuration, and capability testing results' - these are query/monitoring operations with no modification or execution capabilities mentioned.
Documented attack patterns abuse exactly the kind of access ai_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Orchestrator MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for ai_status:
{
"version": "1",
"default": "deny",
"tools": {
"ai_status": {}
}
}ai_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Health monitoring - check AI orchestration system status, model configuration, and capability testing results. Useful for debugging or verifying system readiness. It is categorised as a Read tool in the Orchestrator MCP MCP Server, which means it retrieves data without modifying state.
Register the Orchestrator MCP server in PolicyLayer and add a rule for ai_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 Orchestrator MCP. Nothing to install.
ai_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ai_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.
Set action: deny in the PolicyLayer policy for ai_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.
ai_status is provided by the Orchestrator MCP server (phoenixrr2113/orchestrator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Orchestrator MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Orchestrator MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.