update_calendar_event · OOSDK MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_calendar_event does on OOSDK MCP Server

AI agents use update_calendar_event to create or update resources in OOSDK MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OOSDK MCP Server environment.

WHY IT NEEDS A POLICY

Why update_calendar_event needs a policy

Updating a calendar event is a reversible modification (Write category) rather than Read or Destructive. Severity is medium because calendar changes affect scheduling and availability for potentially multiple participants, but the blast radius is limited compared to financial or destructive operations. Confidence is 0.85 rather than higher due to empty description, but the tool name and context are clear.

From the tool's definition Tool name 'update_calendar_event' indicates modification of calendar data. No description provided, but sibling tools on this server include destructive operations (delete_calendar_event, delete_company_document), establishing this is an…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_calendar_event Rate-limited

update_calendar_event stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_calendar_event": {
      "limits": [
        {
          "counter": "update_calendar_event_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 update_calendar_event

What does the update_calendar_event tool do? +

update_calendar_event. It is categorised as a Write tool in the OOSDK MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_calendar_event? +

Register the OOSDK MCP Server MCP server in PolicyLayer and add a rule for update_calendar_event: 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 update_calendar_event? +

update_calendar_event is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_calendar_event? +

Yes. Add a rate_limit block to the update_calendar_event 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 update_calendar_event completely? +

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

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