Get current system status and health metrics
AI agents call get_system_status to retrieve information from Multi Agent 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 status and health metrics without side effects. It performs a read-only operation to obtain observability data, fitting the Read category. The severity is low since status queries pose minimal risk even if misused by an AI agent—they cannot modify infrastructure, trigger deployments, or cause data loss.
From the tool's definition Tool name 'get_system_status' and description 'Get current system status and health metrics' indicate a query/retrieval operation that reads monitoring data without modifying or executing external operations.
Attacks that exploit this kind of access
Get current system status and health metrics. It is categorised as a Read tool in the Multi Agent Orchestrator MCP MCP Server, which means it retrieves data without modifying state.
Register the Multi Agent Orchestrator MCP server in PolicyLayer and add a rule for get_system_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 Multi Agent Orchestrator MCP. Nothing to install.
get_system_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 get_system_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 get_system_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.
get_system_status is provided by the Multi Agent Orchestrator MCP server (yoriichi-07/multi_orchestrator_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →