AI agents use UpdateOneMessage 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.
The tool modifies existing message records reversibly without deleting them or executing arbitrary code. This is a Write operation with medium severity because unintended message updates in a CRM could affect business communications and data integrity, but changes are reversible and the blast radius is limited to individual messages rather than system-wide operations.
From the tool's definition Tool name 'UpdateOneMessage' and description 'Update One message' indicate modification of existing data. The 'Update' verb combined with sibling tools that use 'createMany' patterns suggests this operates on CRM message data within Twenty's system.
Documented attack patterns abuse exactly the kind of access UpdateOneMessage 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 UpdateOneMessage:
{
"version": "1",
"default": "deny",
"tools": {
"UpdateOneMessage": {
"limits": [
{
"counter": "updateonemessage_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}UpdateOneMessage 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 One message. 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 UpdateOneMessage: 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.
UpdateOneMessage 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 UpdateOneMessage 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 UpdateOneMessage. 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.
UpdateOneMessage 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.