// SCAN REPORT

Luma Events

4 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 1 Jul 2026

1 can modify or destroy data

3 read-only

4 tools total

Community server · catalogue entry verified 01/07/2026

How to control Luma Events ↓

TOOL MAP

What Luma Events exposes to your agents

Read (3) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Luma Events tools

Write · Low set_preferences The tool name 'set_preferences' indicates it creates or modifies user preference data, consistent with the Write category.

1 of Luma Events's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Luma Events

PolicyLayer is an MCP gateway — it sits between your AI agents and Luma Events, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "set_preferences": {
    "limits": [
      {
        "counter": "set_preferences_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "export_event_ics": {
    "limits": [
      {
        "counter": "export_event_ics_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Luma Events — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON LUMA EVENTS →

Instant setup, no code required.

FULL CATALOGUE

All 4 Luma Events tools

WRITE 1 tools

Write set_preferences set_preferences

READ 3 tools

Read export_event_ics Generate an ICS calendar string for a Luma event (Add to Calendar). Read get_event Get full details for a single Luma event. Read search_events search_events

FAQ

Questions about Luma Events

How do I prevent bulk modifications through Luma Events? +

The Luma Events server has 1 write tools including set_preferences. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Luma Events.

How many tools does the Luma Events MCP server expose? +

4 tools across 2 categories: Read, Write. 3 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Luma Events? +

Register the Luma Events MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Luma Events tool call.

Deterministic rules across all 4 Luma Events tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON LUMA EVENTS →

Instant setup, no code required.

4 Luma Events tools catalogued and risk-classified — across an index of 43,000+ MCP servers.