Get full details of a single calendar event by UID. Returns
AI agents call ical__get_event to retrieve information from Mcp Ical Swift 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 by unique identifier without modifying, creating, deleting, or executing operations. It is a straightforward read operation. The severity is low because calendar event metadata poses minimal risk even if exposed to an AI agent; the worst outcome is information disclosure of calendar contents.
From the tool's definition Tool name is 'ical__get_event' and description states 'Get full details of a single calendar event by UID. Returns' — the verb 'Get' and use case of retrieving a single event's details indicates a read-only operation with no side effects.
Attacks that exploit this kind of access
Get full details of a single calendar event by UID. Returns. It is categorised as a Read tool in the Mcp Ical Swift MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ical Swift MCP server in PolicyLayer and add a rule for ical__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 Mcp Ical Swift. Nothing to install.
ical__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 ical__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 ical__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.
ical__get_event is provided by the Mcp Ical Swift MCP server (sealjay/mcp-ical-swift). 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 →