New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_event

Get detailed information about a single calendar event by its UID, including full description, attendees, and recurrence rules.

Low RISK CLASS
Category Read
Parameters 22 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiquila-nextcloud-mcp-server/get-event.md

What get_event does on AIquila — Nextcloud MCP Server

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

ParameterTypeRequiredDescription
uid string Yes The UID of the event
calendarName string Yes The calendar name. Use list_calendars to find available calendar names.

Parameters from the server's own tool schema.

Why get_event is rated Low

This tool retrieves and queries calendar event details (description, attendees, recurrence rules) without modifying, deleting, or executing any operations. It is a read-only operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'get_event' and description 'Get detailed information about a single calendar event by its UID' indicates retrieval of existing data with no side effects.

Questions about get_event

What does the get_event tool do? +

Get detailed information about a single calendar event by its UID, including full description, attendees, and recurrence rules. It is categorised as a Read tool in the AIquila — Nextcloud MCP Server MCP Server, which means it retrieves data without modifying state.

What parameters does get_event accept? +

get_event accepts 2 parameters: uid, calendarName. Required: uid, calendarName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_event? +

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

What risk level is get_event? +

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

Can I rate-limit get_event? +

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

How do I block get_event completely? +

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

What MCP server provides get_event? +

get_event is provided by the AIquila — Nextcloud MCP Server MCP server (elgorro/aiquila). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on AIquila — Nextcloud MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of AIquila — Nextcloud MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.