AI agents call list_calendly_events 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 |
|---|---|---|---|
sort | string | — | e.g. start_time:asc |
count | number | — | |
status | string | — | active or canceled |
api_key | string | — | |
user_uri | string | — | User URI (auto-resolved if omitted) |
max_start_time | string | — | ISO 8601 datetime |
min_start_time | string | — | ISO 8601 datetime |
Parameters from the server's own tool schema.
This tool queries and returns calendar event data belonging to the authenticated user. It retrieves existing information without creating, modifying, deleting, or executing external operations. The blast radius if misused by an AI agent is low—it only exposes the user's own calendar schedule, which is informational. No data is altered, no commands are executed, and no financial transactions are involved.
From the tool's definition Tool name and description explicitly state 'List scheduled events' — a retrieval operation with no modification or side effects. The verb 'list' is a classic Read operation.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
List scheduled events for the authenticated Calendly user. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
list_calendly_events accepts 7 parameters: sort, count, status, api_key, user_uri, max_start_time, min_start_time. 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 list_calendly_events: 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.
list_calendly_events 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 list_calendly_events 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 list_calendly_events. 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.
list_calendly_events 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 →