AI agents call defense_remove 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.
Removing a deployed defense rule is destructive because it cannot be easily undone and eliminates an active security control. This has high severity in a governance context—disabling defenses could expose systems to threats. The tool operates within a governed system (Novyx-mcp) with audit trails, but the action itself is fundamentally irreversible and reduces security posture.
From the tool's definition Tool name 'defense_remove' combined with description 'Remove a deployed defense rule' indicates irreversible deletion of a security control configuration.
Documented attack patterns abuse exactly the kind of access defense_remove 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 defense_remove:
{
"version": "1",
"default": "deny",
"hide": [
"defense_remove"
]
}defense_remove disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a deployed defense rule. 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.
Register the Novyx MCP server in PolicyLayer and add a rule for defense_remove: 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.
defense_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the defense_remove 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.
Set action: deny in the PolicyLayer policy for defense_remove. 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.
defense_remove 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.
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.