AI agents use create_meeting to create or update resources in EspoCRM-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EspoCRM-MCP environment.
Creating a meeting is a Write operation because it generates a new entity in the CRM database. While reversible (meetings can be deleted), the tool modifies state by inserting data. Severity is medium because misuse could spam the system with unwanted meetings or clutter records, but cannot delete data, execute code, or commit financial actions. High confidence based on clear intent from both name and description.
From the tool's definition Tool name is "create_meeting" and description states "Create a new meeting in EspoCRM" — this is a create operation that adds a new record to the system.
Documented attack patterns abuse exactly the kind of access create_meeting gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and EspoCRM-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_meeting:
{
"version": "1",
"default": "deny",
"tools": {
"create_meeting": {
"limits": [
{
"counter": "create_meeting_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_meeting 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 a new meeting in EspoCRM. It is categorised as a Write tool in the EspoCRM-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the EspoCRM- MCP server in PolicyLayer and add a rule for create_meeting: 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 EspoCRM-MCP. Nothing to install.
create_meeting 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_meeting 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_meeting. 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_meeting is provided by the EspoCRM- MCP server (zaphod-black/espomcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 46 EspoCRM-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
46 EspoCRM-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.