add_calendar_event · MCP Multi-Agent Server MCP

WHAT IT DOES

What add_calendar_event does on MCP Multi-Agent Server

AI agents use add_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 add_calendar_event needs a policy

This tool creates new calendar events, which is a reversible modification operation (events can be deleted or edited). It does not execute arbitrary commands, delete data irreversibly, or move money. The medium severity reflects potential for calendar disruption (false meetings, scheduling conflicts) but limited blast radius compared to destructive or financial operations.

From the tool's definition Tool name 'add_calendar_event' indicates creation of calendar data. Sibling tool 'delete_calendar_event' confirms calendar manipulation is supported. The 'add' verb typically indicates a Write operation that creates or appends data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_calendar_event Rate-limited

add_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": {
    "add_calendar_event": {
      "limits": [
        {
          "counter": "add_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 add_calendar_event

What does the add_calendar_event tool do? +

add_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 add_calendar_event? +

Register the MCP Multi-Agent Server MCP server in PolicyLayer and add a rule for add_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 add_calendar_event? +

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

Can I rate-limit add_calendar_event? +

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

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

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