createOneCalendarEventParticipant
A write tool on the Twenty MCP server.
This record as markdown: /tools/jdu278-twenty-mcp-server/createonecalendareventparticipant.md
What createOneCalendarEventParticipant does on Twenty MCP Server
AI agents use createOneCalendarEventParticipant to create or update resources in Twenty MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Twenty MCP Server environment.
Why createOneCalendarEventParticipant is rated Medium
This tool creates a calendar event participant entry, which is a reversible modification of CRM data. It does not execute arbitrary code, delete data, or involve financial transactions. The severity is medium because the blast radius involves adding participants to calendar events in a CRM system, which could affect scheduling and organizational workflows but can be easily undone by removing the participant.
From the tool's definition Tool name contains 'createOne' which indicates creation of a new entity; description states 'Create One calendarEventParticipant'; sibling tools follow the pattern of create operations (createManyAttachments, createManyCompanies, etc.)
Attacks that exploit this kind of access
The rule that runs createOneCalendarEventParticipant 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 createOneCalendarEventParticipant, this is the rule to start with:
createOneCalendarEventParticipant stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 createOneCalendarEventParticipant call is checked against it from then on.
Questions about createOneCalendarEventParticipant
createOneCalendarEventParticipant is a write tool on the Twenty MCP Server MCP server. It is categorised as a Write tool in the Twenty MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Twenty MCP Server MCP server in PolicyLayer and add a rule for createOneCalendarEventParticipant: 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.
createOneCalendarEventParticipant is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the createOneCalendarEventParticipant 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 createOneCalendarEventParticipant. 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.
createOneCalendarEventParticipant 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