Use this endpoint to create or update people, companies and other records. A matching attribute is used to search for existing records. If a record is found with the same value for the matching attribute, that record will be updated. If no record with the same value for the matching attribute is ...
AI agents use putv2objectsrecords to create or update resources in Attio — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Attio environment.
This tool performs reversible create and update operations on records in the Attio CRM system. It does not delete data (which would be Destructive) and does not move money (which would be Financial). While it modifies data, the operations are reversible through subsequent updates, placing it in the Write category.
From the tool's definition Tool description explicitly states it is used to "create or update people, companies and other records." The description confirms write operations: "a new record will be created" or "that record will be updated."
Documented attack patterns abuse exactly the kind of access putv2objectsrecords gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Attio, and nothing reaches the server without passing your rules. This is the rule we recommend for putv2objectsrecords:
{
"version": "1",
"default": "deny",
"tools": {
"putv2objectsrecords": {
"limits": [
{
"counter": "putv2objectsrecords_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}putv2objectsrecords 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.
Use this endpoint to create or update people, companies and other records. A matching attribute is used to search for existing records. If a record is found with the same value for the matching attribute, that record will be updated. If no record with the same value for the matching attribute is found, a new record will be created instead. If you would like to avoid matching, please use the [Create record endpoint](/rest-api/endpoint-reference/records/create-a-record). If the matching attribute is a multiselect attribute, new values will be added and existing values will not be deleted. For any other multiselect attribute, all values will be either created or deleted as necessary to match the list of supplied values. Required scopes: \. It is categorised as a Write tool in the Attio MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Attio MCP server in PolicyLayer and add a rule for putv2objectsrecords: 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. Nothing to install.
putv2objectsrecords 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 putv2objectsrecords 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 putv2objectsrecords. 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.
putv2objectsrecords is provided by the Attio MCP server (itsbrex/attio-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Attio, 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.
57 Attio tools catalogued and risk-classified — across an index of 43,000+ MCP servers.