respond_to_invite · Calendar MCP Server MCP: Risk & Policy

WHAT IT DOES

What respond_to_invite does on Calendar MCP Server

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

WHY IT NEEDS A POLICY

Why respond_to_invite needs a policy

This tool creates or modifies reversible state on the calendar—a meeting RSVP can be changed later. It does not execute arbitrary code, delete data irreversibly, move money, or trigger external operations beyond sending a calendar response. The action is a standard Write operation: it updates an attendee's response status on an event, which is a common, reversible calendar management task.

From the tool's definition Tool modifies calendar state by accepting, declining, or marking tentative a meeting invitation; the description explicitly states it 'Respond[s] to a meeting invitation (accept, decline, or tentative)' with optional response message.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

respond_to_invite Rate-limited

respond_to_invite 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": {
    "respond_to_invite": {
      "limits": [
        {
          "counter": "respond_to_invite_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 Calendar MCP Server, so you can run agents against it safely.

FAQ

Questions about respond_to_invite

What does the respond_to_invite tool do? +

Respond to a meeting invitation (accept, decline, or tentative). Optionally include a response message. It is categorised as a Write tool in the Calendar 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 respond_to_invite? +

Register the Calendar MCP Server MCP server in PolicyLayer and add a rule for respond_to_invite: 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 Calendar MCP Server. Nothing to install.

What risk level is respond_to_invite? +

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

Can I rate-limit respond_to_invite? +

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

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

respond_to_invite is provided by the Calendar MCP Server MCP server (rauf543/calendar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.