登録済みの子サーバーの状態を返します（起動済み/失敗/停止中など）。
AI agents call get_child_status to retrieve information from MCP Gateway (Parent MCP Server) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query/status-check operation that retrieves state information about child server processes. It has no capability to modify, execute, delete, or affect system state—only to observe and report current status. This falls squarely into the Read category with low severity, as the worst outcome is stale or inaccurate status information being returned to the user.
From the tool's definition Tool description (translated from Japanese) states it 'returns the status of registered child servers (started/failed/stopped, etc.)'. The verb 'returns' indicates data retrieval with no side effects.
Attacks that exploit this kind of access
登録済みの子サーバーの状態を返します（起動済み/失敗/停止中など）。. It is categorised as a Read tool in the MCP Gateway (Parent MCP Server) MCP Server, which means it retrieves data without modifying state.
Register the MCP Gateway (Parent MCP Server) MCP server in PolicyLayer and add a rule for get_child_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 MCP Gateway (Parent MCP Server). Nothing to install.
get_child_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_child_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_child_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_child_status is provided by the MCP Gateway (Parent MCP Server) MCP server (tomcat2357/mcpgateway). 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 →