run_calendar_agent · OOSDK MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_calendar_agent does on OOSDK MCP Server

AI agents invoke run_calendar_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.

WHY IT NEEDS A POLICY

Why run_calendar_agent needs a policy

This tool executes arbitrary tasks delegated to a Calendar Agent without explicit bounds on what operations are permitted. Calendar operations can include creating, modifying, or deleting events—spanning Write and Destructive categories—but the tool itself is an execution wrapper that invokes an agent with user-provided inputs. The actual risk depends on what the agent is instructed to do.

From the tool's definition Tool name 'run_calendar_agent' combined with description indicating direct task execution to a Calendar Agent ('Calendar Agent에게 직접 작업을 요청합니다' = 'Request work directly to Calendar Agent').

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_calendar_agent Rate-limited

run_calendar_agent stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_calendar_agent": {
      "limits": [
        {
          "counter": "run_calendar_agent_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches OOSDK MCP Server, so you can run agents against it safely.

FAQ

Questions about run_calendar_agent

What does the run_calendar_agent tool do? +

Calendar 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.

How do I enforce a policy on run_calendar_agent? +

Register the OOSDK MCP Server MCP server in PolicyLayer and add a rule for run_calendar_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.

What risk level is run_calendar_agent? +

run_calendar_agent is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_calendar_agent? +

Yes. Add a rate_limit block to the run_calendar_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.

How do I block run_calendar_agent completely? +

Set action: deny in the PolicyLayer policy for run_calendar_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.

What MCP server provides run_calendar_agent? +

run_calendar_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.