등록된 Agent들의 상세 정보를 반환합니다.
AI agents call get_agent_info 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 and returns metadata about registered agents in the system. It is a pure read operation—querying configuration or status data about agents without creating, modifying, deleting, or executing any actions. The low severity reflects minimal blast radius: disclosure of agent metadata does not directly impact user data, financial systems, or critical operations.
From the tool's definition Tool name 'get_agent_info' and description '등록된 Agent들의 상세 정보를 반환합니다' (returns detailed information of registered agents) indicate a retrieval operation with no modification or side effects.
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 get_agent_info: 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.
get_agent_info 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_agent_info 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_agent_info. 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_agent_info 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 →