update_person
Update an existing person
This record as markdown: /tools/denisalmeida-twenty-crm-mcp/update-person.md
What update_person does on Twenty CRM MCP Server
AI agents use update_person to create or update resources in Twenty CRM MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Twenty CRM MCP Server environment.
Why update_person is rated Medium
This tool modifies existing person records in the CRM system. Updates are reversible (the previous state can be restored), so it falls under Write rather than Destructive. Severity is medium because unauthorized updates to CRM person records could corrupt customer data and business processes, but the impact is limited to a single person record and can be undone.
From the tool's definition Tool name 'update_person' and description 'Update an existing person' indicate modification of existing data.
Attacks that exploit this kind of access
The rule that runs update_person safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Twenty CRM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_person, this is the rule to start with:
update_person 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Twenty CRM MCP Server, apply this rule, and every update_person call is checked against it from then on.
Questions about update_person
Update an existing person. It is categorised as a Write tool in the Twenty CRM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Twenty CRM MCP Server MCP server in PolicyLayer and add a rule for update_person: 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 CRM MCP Server. Nothing to install.
update_person 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_person 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_person. 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_person is provided by the Twenty CRM MCP Server MCP server (denisalmeida/twenty-crm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Twenty CRM MCP Server, and thousands of servers like it.
This server
Across the catalogue