findManyCalendarEventParticipants
order_by, filter, limit, depth, starting_after or ending_before can be provided to request your calendarEventParticipants
This record as markdown: /tools/jdu278-twenty-mcp-server/findmanycalendareventparticipants.md
What findManyCalendarEventParticipants does on Twenty MCP Server
AI agents call findManyCalendarEventParticipants to retrieve information from Twenty MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why findManyCalendarEventParticipants is rated Low
This tool retrieves calendar event participant data with optional filtering and pagination. It performs read-only queries with no side effects. The parameters (order_by, filter, limit, depth, starting_after, ending_before) are consistent with data retrieval and do not modify state. The severity is low because unauthorized access to calendar participant information has limited blast radius in typical CRM contexts.
From the tool's definition Tool name 'findManyCalendarEventParticipants' and description indicating querying capabilities with parameters like **filter**, **limit**, **order_by** are standard for retrieval operations.
Attacks that exploit this kind of access
The rule that runs findManyCalendarEventParticipants safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Twenty MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For findManyCalendarEventParticipants, this is the rule to start with:
findManyCalendarEventParticipants 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 Twenty MCP Server, apply this rule, and every findManyCalendarEventParticipants call is checked against it from then on.
Questions about findManyCalendarEventParticipants
order_by, filter, limit, depth, starting_after or ending_before can be provided to request your calendarEventParticipants. It is categorised as a Read tool in the Twenty MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Twenty MCP Server MCP server in PolicyLayer and add a rule for findManyCalendarEventParticipants: 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 Twenty MCP Server. Nothing to install.
findManyCalendarEventParticipants 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 findManyCalendarEventParticipants 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 findManyCalendarEventParticipants. 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.
findManyCalendarEventParticipants is provided by the Twenty MCP Server MCP server (jdu278/twenty-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Twenty MCP Server, and thousands of servers like it.
This server
Across the catalogue