Get full details of a single CalDAV event by its href.
AI agents call calendar_get_event to retrieve information from Pyfastmail without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves calendar event data without creating, modifying, deleting, or executing anything. It is a straightforward query operation that reads existing information. While the server grants broad access to Fastmail accounts, this specific tool performs no destructive or consequential actions.
From the tool's definition Tool name is 'calendar_get_event' and description states 'Get full details of a single CalDAV event by its href' — the verb 'Get' and the absence of any modification language indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get full details of a single CalDAV event by its href. It is categorised as a Read tool in the Pyfastmail MCP Server, which means it retrieves data without modifying state.
Register the Pyfastmail MCP server in PolicyLayer and add a rule for calendar_get_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 Pyfastmail. Nothing to install.
calendar_get_event is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the calendar_get_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.
Set action: deny in the PolicyLayer policy for calendar_get_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.
calendar_get_event is provided by the Pyfastmail MCP server (pjosols/pyfastmail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →