Low Risk

caldav_get_event_by_uid

Get a specific event by its UID

How to control caldav_get_event_by_uid ↓

What caldav_get_event_by_uid does on CalDAV MCP Server

AI agents call caldav_get_event_by_uid to retrieve information from CalDAV MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why caldav_get_event_by_uid needs a policy

This tool retrieves a specific calendar event by unique identifier (UID) without creating, modifying, deleting, or executing any actions. It is purely a read operation with minimal security impact—calendar data retrieval poses no risk of data loss, financial impact, or unintended side effects.

From the tool's definition Tool name contains 'get', description states 'Get a specific event', indicating data retrieval with no modification. The UID-based lookup is a read-only query operation on calendar events.

Documented attack patterns abuse exactly the kind of access caldav_get_event_by_uid gives an agent:

How to control caldav_get_event_by_uid

PolicyLayer is an MCP gateway — it sits between your AI agents and CalDAV MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for caldav_get_event_by_uid:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "caldav_get_event_by_uid": {}
  }
}

caldav_get_event_by_uid is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register CalDAV MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about caldav_get_event_by_uid

What does the caldav_get_event_by_uid tool do? +

Get a specific event by its UID. It is categorised as a Read tool in the CalDAV MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on caldav_get_event_by_uid? +

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

What risk level is caldav_get_event_by_uid? +

caldav_get_event_by_uid is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit caldav_get_event_by_uid? +

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

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

caldav_get_event_by_uid is provided by the CalDAV MCP Server MCP server (madbonez/caldav-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CalDAV MCP Server tool call.

Start from CalDAV MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

8 CalDAV MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.