update_calendar_event · MCP Multi-Agent Server MCP

WHAT IT DOES

What update_calendar_event does on MCP Multi-Agent Server

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

WHY IT NEEDS A POLICY

Why update_calendar_event needs a policy

The tool modifies existing calendar events. While the description is empty, the name and context of sibling tools (add_calendar_event, delete_calendar_event) clearly establish this as a calendar management function. Updates are reversible, so it falls under Write rather than Destructive.

From the tool's definition Tool name 'update_calendar_event' indicates modification of calendar data. Sibling tool 'delete_calendar_event' is present, confirming this server manages calendar resources. Update operations are reversible modifications (Write category).

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 MCP Multi-Agent 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 MCP Multi-Agent 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 MCP Multi-Agent 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 MCP Multi-Agent 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 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.