AI agents call get_calendly_event to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | — | |
event_uuid | string | Yes | Event UUID |
Parameters from the server's own tool schema.
This tool retrieves and queries calendar event information without creating, modifying, deleting, or executing any operations. It is a simple read operation that returns event details. The blast radius of misuse is low — exposing event details could leak scheduling information, but does not enable destructive, financial, or code execution actions.
From the tool's definition Tool name and description: 'Get details of a single Calendly scheduled event' — uses 'Get' which indicates retrieval of existing event data with no modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Get details of a single Calendly scheduled event. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
get_calendly_event accepts 2 parameters: api_key, event_uuid. Required: event_uuid. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for get_calendly_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 UnClick. Nothing to install.
get_calendly_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 get_calendly_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 get_calendly_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.
get_calendly_event is provided by the UnClick MCP server (@unclick/mcp-server). 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 →