calendly_list_invitees
AI agents call calendly_list_invitees to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or queries a list of invitees from Calendly events, producing no side effects or data modifications. The 'list' verb is a strong indicator of read-only behavior. Confidence is slightly reduced (0.85 rather than 0.95) because the description is empty, preventing direct confirmation of the tool's exact scope and whether it might have any secondary effects.
From the tool's definition Tool name 'calendly_list_invitees' uses the verb 'list', which indicates data retrieval. The context of Calendly (a scheduling platform) and the absence of mutation keywords (create, update, delete) further support a read operation.
Attacks that exploit this kind of access
calendly_list_invitees. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for calendly_list_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 Integrations MCP. Nothing to install.
calendly_list_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 calendly_list_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 calendly_list_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.
calendly_list_invitees is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). 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 →