Report Agent에게 직접 작업을 요청합니다.
AI agents invoke run_report_agent to trigger actions in OOSDK MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers execution of an autonomous Report Agent to perform work on behalf of the user. While the description is minimal and in Korean, the verb 'run' combined with 'agent' indicates dynamic code/agent execution whose effects depend on what tasks are submitted.
From the tool's definition Tool description states '직접 작업을 요청합니다' (directly request work/tasks to be performed). The name 'run_report_agent' indicates execution of an agent that performs operations.
Attacks that exploit this kind of access
Report Agent에게 직접 작업을 요청합니다. It is categorised as a Execute tool in the OOSDK MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OOSDK MCP Server MCP server in PolicyLayer and add a rule for run_report_agent: 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.
run_report_agent is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_report_agent 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 run_report_agent. 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.
run_report_agent 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 →