AI agents use update_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.
This tool creates or modifies data reversibly within EspoCRM by updating an existing meeting record. It does not delete data (which would be Destructive), execute arbitrary code (which would be Execute), or move money (which would be Financial). Updates to meeting records are reversible through subsequent updates, placing it clearly in the Write category.
From the tool's definition Tool name is 'update_meeting' and description states 'Update an existing meeting in EspoCRM'. The verb 'update' indicates modification of existing data.
Documented attack patterns abuse exactly the kind of access update_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 update_meeting:
{
"version": "1",
"default": "deny",
"tools": {
"update_meeting": {
"limits": [
{
"counter": "update_meeting_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_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.
Update an existing 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 update_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.
update_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 update_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 update_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.
update_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.