Critical Risk →

deletev2commentsbycommentid

Deletes a comment by ID. If deleting a comment at the head of a thread, all messages in the thread are also deleted. Required scopes: \

How to control deletev2commentsbycommentid ↓

What deletev2commentsbycommentid does on Attio

AI agents call deletev2commentsbycommentid to permanently remove resources in Attio — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why deletev2commentsbycommentid needs a policy

This tool irreversibly deletes comments and, critically, can cascade-delete entire comment threads if the head comment is targeted. This is a destructive, unrecoverable operation with potentially broad blast radius affecting all replies in a thread.

From the tool's definition Deletes a comment by ID. If deleting a comment at the head of a thread, all messages in the thread are also deleted.

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

How to control deletev2commentsbycommentid

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "deletev2commentsbycommentid"
  ]
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about deletev2commentsbycommentid

What does the deletev2commentsbycommentid tool do? +

Deletes a comment by ID. If deleting a comment at the head of a thread, all messages in the thread are also deleted. 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 deletev2commentsbycommentid? +

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

deletev2commentsbycommentid 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 deletev2commentsbycommentid? +

Yes. Add a rate_limit block to the deletev2commentsbycommentid 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 deletev2commentsbycommentid completely? +

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

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

Free to start. No card required.

57 Attio tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.