OpenAI 서비스 상태를 확인합니다.
AI agents call get_openai_status to retrieve information from MCP Multi-Agent Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves service status information without modifying, executing code, deleting data, or committing financial transactions. It is purely informational and read-only, making it a Read category risk. Severity is low because misuse has minimal blast radius—an attacker could at best gather status information about OpenAI services, which is typically public or low-sensitivity data.
From the tool's definition Tool name 'get_openai_status' and description 'OpenAI 서비스 상태를 확인합니다' (checks OpenAI service status) indicates a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
OpenAI 서비스 상태를 확인합니다. It is categorised as a Read tool in the MCP Multi-Agent Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Multi-Agent Server MCP server in PolicyLayer and add a rule for get_openai_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 Multi-Agent Server. Nothing to install.
get_openai_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_openai_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_openai_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_openai_status is provided by the MCP Multi-Agent Server MCP server (sunnylabtv-crypto/ai_mcp_multi_agent-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 →