Critical Risk →

delete-toolset

Delete a saved toolset configuration

Part of the Hypertool server.

delete-toolset can permanently delete data in Hypertool, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE HYPERTOOL →

Free to start. No card required.

AI agents may call delete-toolset to permanently remove or destroy resources in Hypertool. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call delete-toolset in a loop, permanently destroying resources in Hypertool. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-toolset"
  ]
}

See the full Hypertool policy for all 19 tools.

Get this rule live on your own Hypertool server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY HYPERTOOL →

View all 19 tools →

These attack patterns abuse exactly the kind of access delete-toolset gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so delete-toolset only ever does what you allow.

SECURE HYPERTOOL →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the delete-toolset tool do? +

Delete a saved toolset configuration. It is categorised as a Destructive tool in the Hypertool 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-toolset? +

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

What risk level is delete-toolset? +

delete-toolset 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-toolset? +

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

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

delete-toolset is provided by the Hypertool MCP server (toolprint/hypertool-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Hypertool tool call.

Deterministic rules across all 19 Hypertool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.