deletev2objectsrecordsbyrecordid

THE RISK

Critical Risk

Why deletev2objectsrecordsbyrecordid needs a policy

This tool permanently deletes a record (company, person, etc.) from Attio by its ID. Deletion of CRM records is irreversible and can result in loss of important business data including contact history, relationships, and associated metadata. The high severity reflects the blast radius: an AI agent misusing this tool could systematically delete critical business records.

From the tool's definition 'Deletes a single record (e.g. a company or person) by ID' — explicit deletion of CRM records by ID

Documented attack patterns abuse exactly the kind of access deletev2objectsrecordsbyrecordid gives an agent:

POLICY

How to control deletev2objectsrecordsbyrecordid

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 deletev2objectsrecordsbyrecordid:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "deletev2objectsrecordsbyrecordid"
  ]
}

deletev2objectsrecordsbyrecordid disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Attio — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Attio tools

Destructive deletev2notesbynoteid Delete a single note by ID. Required scopes: \ Destructive deletev2tasksbytaskid Delete a task by ID. Required scopes: \ Destructive deletev2webhooksbywebhookid Delete a webhook by ID. Required scopes: \ Destructive deletev2commentsbycommentid Deletes a comment by ID. If deleting a comment at the head of a thread, all messages in th Destructive deletev2listsentriesbyentryid Deletes a single list entry by its \ Write patchv2attributesbyattribute Updates a single attribute on a given object or list. Required scopes: \ Write patchv2attributesoptionsbyoption Updates a select option on an attribute on either an object or a list. Required scopes: \ Write patchv2listsbylist Updates an existing list. Permissions for the list are controlled with the \

All 57 Attio tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Attio → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about deletev2objectsrecordsbyrecordid

What does the deletev2objectsrecordsbyrecordid tool do? +

Deletes a single record (e.g. a company or person) by ID. Required scopes: \. It is categorised as a Destructive tool in the Attio MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on deletev2objectsrecordsbyrecordid? +

Register the Attio MCP server in PolicyLayer and add a rule for deletev2objectsrecordsbyrecordid: 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.

What risk level is deletev2objectsrecordsbyrecordid? +

deletev2objectsrecordsbyrecordid is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit deletev2objectsrecordsbyrecordid? +

Yes. Add a rate_limit block to the deletev2objectsrecordsbyrecordid 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.

How do I block deletev2objectsrecordsbyrecordid completely? +

Set action: deny in the PolicyLayer policy for deletev2objectsrecordsbyrecordid. 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.

What MCP server provides deletev2objectsrecordsbyrecordid? +

deletev2objectsrecordsbyrecordid 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.

Enforce policy on every Attio tool call.

Start from Attio, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →