Update an existing person in Attio CRM by record ID. You can update name fields (first_name, last_name, full_name), description, and/or LinkedIn URL. Only provided fields will be updated; omitted fields remain unchanged. To manage email addresses, use add_person_email and remove_person_email tool...
AI agents use update_person to create or update resources in Attio Simple MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Attio Simple MCP Server environment.
update_person modifies existing CRM data (person records) by changing name fields, description, or LinkedIn URL. This is a Write action—data is created or modified reversibly without permanent deletion or financial impact.
From the tool's definition Tool description states 'Update an existing person in Attio CRM' and 'Only provided fields will be updated; omitted fields remain unchanged.' This is a reversible modification operation.
Attacks that exploit this kind of access
Update an existing person in Attio CRM by record ID. You can update name fields (first_name, last_name, full_name), description, and/or LinkedIn URL. Only provided fields will be updated; omitted fields remain unchanged. To manage email addresses, use add_person_email and remove_person_email tools instead. Returns the updated person record. It is categorised as a Write tool in the Attio Simple MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Attio Simple 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 Attio Simple 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 Attio Simple MCP Server MCP server (mlemos/attio-simple-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 →