create_event_calendar_file · Events MCP: Risk & Policy

WHAT IT DOES

What create_event_calendar_file does on Events

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

PARAMETERS

Parameter	Type	Required	Description
`status`	string	—	Calendar status, for example CONFIRMED or TENTATIVE.
`event_id`	string	Yes	Event id returned by search, recommendations, plan_night, get_event, or a ticket quote.

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why create_event_calendar_file needs a policy

This tool creates a new calendar entry representing a user's event choice or ticket purchase. This is a write operation that modifies the user's calendar data reversibly—the entry can be edited or deleted later. It does not delete, execute arbitrary code, move money, or have destructive side effects.

From the tool's definition Tool description states it is used to 'add a UPlayground event to their calendar', which involves creating a calendar file or entry.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_event_calendar_file Rate-limited

create_event_calendar_file 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": {
    "create_event_calendar_file": {
      "limits": [
        {
          "counter": "create_event_calendar_file_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 Events, so you can run agents against it safely.

FAQ

Questions about create_event_calendar_file

What does the create_event_calendar_file tool do? +

Use this when a user wants to add a UPlayground event to their calendar after choosing or buying tickets. It is categorised as a Write tool in the Events MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does create_event_calendar_file accept? +

create_event_calendar_file accepts 2 parameters: status, event_id. Required: event_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_event_calendar_file? +

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

What risk level is create_event_calendar_file? +

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

Can I rate-limit create_event_calendar_file? +

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

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

create_event_calendar_file is provided by the Events MCP server (uplayground-events). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.