모든 서비스와 Agent의 현재 상태를 확인합니다.
AI agents call check_all_services_status to retrieve information from OOSDK MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about services and agents without performing any side effects. Status checks are passive monitoring operations that fall squarely into the Read category. The potential blast radius is minimal—even if an AI agent polls this repeatedly, it cannot corrupt data, trigger unwanted actions, or cause financial impact.
From the tool's definition Tool name 'check_all_services_status' and description '모든 서비스와 Agent의 현재 상태를 확인합니다' (which translates to 'Check the current status of all services and Agents') indicates a read-only status/monitoring operation with no data modification, deletion, or external…
Attacks that exploit this kind of access
모든 서비스와 Agent의 현재 상태를 확인합니다. It is categorised as a Read tool in the OOSDK MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OOSDK MCP Server MCP server in PolicyLayer and add a rule for check_all_services_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 OOSDK MCP Server. Nothing to install.
check_all_services_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 check_all_services_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 check_all_services_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.
check_all_services_status is provided by the OOSDK MCP Server MCP server (sunnylabtv-crypto/ai_mcp_multi_agent_oosdk-public). 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 →