Create a new activity in CiviCRM with custom fields
AI agents use create_activity to create or update resources in CiviCRM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CiviCRM MCP Server environment.
This tool creates a new activity record in CiviCRM, which is a standard Write operation—it adds data to the system that can be modified or deleted later. While activities might trigger workflows or notifications, the core function is record creation.
From the tool's definition Tool name 'create_activity' and description 'Create a new activity in CiviCRM' indicate data creation. The sibling tools on this server include both Write operations (create_*) and Destructive operations (delete_*), confirming this server manages CiviCRM…
Attacks that exploit this kind of access
Create a new activity in CiviCRM with custom fields. It is categorised as a Write tool in the CiviCRM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CiviCRM MCP Server MCP server in PolicyLayer and add a rule for create_activity: 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 CiviCRM MCP Server. Nothing to install.
create_activity 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 create_activity 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 create_activity. 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.
create_activity is provided by the CiviCRM MCP Server MCP server (johncallhub/civicrm-mcp-server). 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 →