pfsense_delete_diagnostics_config_history_revisions
AI agents call pfsense_delete_diagnostics_config_history_revisions to permanently remove resources in Pfsense — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes diagnostic configuration history revisions, which cannot be undone. Deletion of system audit trails and configuration history is a destructive operation with critical severity because (1) it irreversibly removes records, (2) it could eliminate evidence of system changes or breaches, (3) it affects system integrity and compliance, and (4) in the context of a firewall managing critical…
From the tool's definition Tool name includes 'delete_diagnostics_config_history_revisions' which indicates permanent removal of configuration history records from pfSense. The 'delete' action combined with 'history_revisions' shows irreversible data destruction.
Attacks that exploit this kind of access
pfsense_delete_diagnostics_config_history_revisions. It is categorised as a Destructive tool in the Pfsense MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_delete_diagnostics_config_history_revisions: 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 Pfsense. Nothing to install.
pfsense_delete_diagnostics_config_history_revisions 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 pfsense_delete_diagnostics_config_history_revisions 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 pfsense_delete_diagnostics_config_history_revisions. 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.
pfsense_delete_diagnostics_config_history_revisions is provided by the Pfsense MCP server (abl030/pfsense-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 →