list_calendly_invitees
List invitees for a Calendly scheduled event.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/list-calendly-invitees.md
What list_calendly_invitees does on UnClick
AI agents call list_calendly_invitees to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
count | number | — | |
status | string | — | active or canceled |
api_key | string | — | |
event_uuid | string | Yes | Event UUID |
Parameters from the server's own tool schema.
Why list_calendly_invitees is rated Low
This tool retrieves information about invitees for a Calendly event. It performs a query operation that returns existing data without creating, modifying, deleting, or executing any actions. The blast radius is minimal — the worst-case misuse would be unauthorized viewing of attendee information, which does not affect system state or enable further damaging actions.
From the tool's definition Tool name contains 'list' and description states 'List invitees' — both indicate data retrieval with no modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs list_calendly_invitees safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_calendly_invitees, this is the rule to start with:
list_calendly_invitees is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every list_calendly_invitees call is checked against it from then on.
Questions about list_calendly_invitees
List invitees for a Calendly scheduled event. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
list_calendly_invitees accepts 4 parameters: count, status, 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 list_calendly_invitees: 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_invitees 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_invitees 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_invitees. 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_invitees 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue