Delete a service and its filter code.
AI agents call delete_nfproxy_service to permanently remove resources in Firegex — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a service and associated filter code from a firewall system. Deletion is irreversible and has high blast radius in a firewall/proxy context: an AI agent could disable security controls or remove critical network services. Although confined to firewall rule management (not arbitrary system data), the destructive nature and security-critical context warrant 'high' severity.
From the tool's definition Tool name contains 'delete' and description states 'Delete a service and its filter code' — irreversible removal of configuration and code.
Attacks that exploit this kind of access
Delete a service and its filter code. It is categorised as a Destructive tool in the Firegex MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Firegex MCP server in PolicyLayer and add a rule for delete_nfproxy_service: 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 Firegex. Nothing to install.
delete_nfproxy_service 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 delete_nfproxy_service 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 delete_nfproxy_service. 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.
delete_nfproxy_service is provided by the Firegex MCP server (umbra2728/firegex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →