delete_td_node

DESTRUCTIVE by default: permanently remove one node from the project by path (a COMP also takes its children with it); this cannot be undone via the API. Prefer mode:

SERVERAos SOURCE@hybridlabor-api/aos

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hybridlabor-api-aos/delete-td-node.md

WHAT IT DOES

What delete_td_node does on Aos

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

RISK

Why delete_td_node is rated Critical

Irreversibly deletes nodes and their children with no undo capability, representing maximum data loss risk.

From the tool's definition permanently remove one node from the project; this cannot be undone via the API

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_td_node safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_td_node, this is the rule to start with:

delete_td_node Hidden

delete_td_node is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every delete_td_node call is checked against it from then on.

FAQ

Questions about delete_td_node

What does the delete_td_node tool do? +

DESTRUCTIVE by default: permanently remove one node from the project by path (a COMP also takes its children with it); this cannot be undone via the API. Prefer mode:. It is categorised as a Destructive tool in the Aos 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 delete_td_node? +

Register the Aos MCP server in PolicyLayer and add a rule for delete_td_node: 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 Aos. Nothing to install.

What risk level is delete_td_node? +

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

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

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

delete_td_node is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aos, and thousands of servers like it.

This server

All 719 Aos tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →