AI agents use createManyCalendarEvents 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.
This tool creates new calendar event records in Twenty CRM. Creation of data is reversible (records can be deleted), so it falls under Write. Severity is medium because bulk creation could spam the calendar with many entries, but it does not execute code or irreversibly destroy data.
From the tool's definition "Create Many calendarEvents" - creates multiple calendar event records in the CRM
Documented attack patterns abuse exactly the kind of access createManyCalendarEvents gives an agent:
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 createManyCalendarEvents:
{
"version": "1",
"default": "deny",
"tools": {
"createManyCalendarEvents": {
"limits": [
{
"counter": "createmanycalendarevents_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createManyCalendarEvents 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.
Free to start. No card required.
Create Many calendarEvents. 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 createManyCalendarEvents: 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.
createManyCalendarEvents 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 createManyCalendarEvents 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 createManyCalendarEvents. 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.
createManyCalendarEvents 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.
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.