Critical Risk →

delete_policy

delete_policy

How to control delete_policy ↓

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

Critical Risk

Although the description is empty (lowering confidence from 0.95 to 0.85), the tool name itself clearly indicates a destructive action. Deleting policies in a governed system is irreversible and could disable critical approval workflows, audit controls, or rollback mechanisms. This is more severe than Write (reversible modification) because policy deletion removes governance guardrails.

From the tool's definition Tool name is 'delete_policy'. The verb 'delete' combined with the object 'policy' indicates irreversible removal of governance rules.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and Novyx, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_policy:

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

delete_policy 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 Novyx — 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.

Go deeper

What does the delete_policy tool do? +

delete_policy. It is categorised as a Destructive tool in the Novyx 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_policy? +

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

What risk level is delete_policy? +

delete_policy 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_policy? +

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

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

delete_policy is provided by the Novyx MCP server (novyxlabs/novyx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Novyx tool call.

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

Free to start. No card required.

120 Novyx tools catalogued and risk-classified — across an index of 42,500+ 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.