delete_learning

Delete a learning by key. Use when a learning is outdated or incorrect.

SERVERNodebench SOURCEnodebench-mcp

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/io-github-homenshum-nodebench/delete-learning.md

WHAT IT DOES

What delete_learning does on Nodebench

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

RISK

Why delete_learning is rated Critical

This tool irreversibly deletes data (a learning record) and cannot be undone. Even though the impact is scoped to a single learning record rather than bulk or critical data, deletion operations are categorized as Destructive.

From the tool's definition Tool name is 'delete_learning' and description states 'Delete a learning by key'. The verb 'delete' combined with 'by key' indicates irreversible removal of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_learning safely

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

delete_learning Hidden

delete_learning 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_learning"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about delete_learning

What does the delete_learning tool do? +

Delete a learning by key. Use when a learning is outdated or incorrect. It is categorised as a Destructive tool in the Nodebench 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_learning? +

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

What risk level is delete_learning? +

delete_learning 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_learning? +

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

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

delete_learning is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench 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 code and CI agents →Blast radius →Tool call approval →