Medium Risk

createOneCalendarEventParticipant

Create One calendarEventParticipant

How to control createOneCalendarEventParticipant ↓

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.

Medium Risk

Why createOneCalendarEventParticipant needs a policy

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.)

Documented attack patterns abuse exactly the kind of access createOneCalendarEventParticipant gives an agent:

How to control createOneCalendarEventParticipant

PolicyLayer is an MCP gateway — it sits between your AI agents and Twenty MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for createOneCalendarEventParticipant:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "createOneCalendarEventParticipant": {
      "limits": [
        {
          "counter": "createonecalendareventparticipant_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

  1. Create a free account and register Twenty MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about createOneCalendarEventParticipant

What does the createOneCalendarEventParticipant tool do? +

Create One calendarEventParticipant. 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.

How do I enforce a policy on createOneCalendarEventParticipant? +

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.

What risk level is createOneCalendarEventParticipant? +

createOneCalendarEventParticipant is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit createOneCalendarEventParticipant? +

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.

How do I block createOneCalendarEventParticipant completely? +

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.

What MCP server provides createOneCalendarEventParticipant? +

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.

Enforce policy on every Twenty MCP Server tool call.

Start from Twenty MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

219 Twenty MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.