Create a new person in Attio CRM. You must provide at least one name field (first_name, last_name, or full_name) or at least one email address. All fields are optional, but you need either a name or email to identify the person. Returns the created person record including the new record_id.
AI agents use create_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.
This tool creates new records in a CRM database, which is a Write operation (data creation). It is reversible through deletion or modification, so not Destructive. Severity is medium because: (1) it creates persistent records in a production CRM system, (2) mass creation by a misguided agent could pollute the database with unwanted contacts, and (3) while problematic, CRM record creation doesn't directly impact…
From the tool's definition Tool description states 'Create a new person in Attio CRM' and 'Returns the created person record including the new record_id', indicating irreversible data creation in a CRM system.
Attacks that exploit this kind of access
Create a new person in Attio CRM. You must provide at least one name field (first_name, last_name, or full_name) or at least one email address. All fields are optional, but you need either a name or email to identify the person. Returns the created person record including the new record_id. 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 create_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.
create_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 create_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 create_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.
create_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 →