Find all firewall rules that block or reject traffic
AI agents call find_blocked_rules to retrieve information from pfSense Enhanced MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries firewall rules to return information about which rules currently block or reject traffic. It has no side effects—it does not create, modify, delete, execute commands, or move money. It is a straightforward data retrieval operation similar to a search or list function.
From the tool's definition Tool name 'find_blocked_rules' and description 'Find all firewall rules that block or reject traffic' indicate a query/search operation that retrieves and lists existing firewall configuration data without modification or execution.
Attacks that exploit this kind of access
Find all firewall rules that block or reject traffic. It is categorised as a Read tool in the pfSense Enhanced MCP Server MCP Server, which means it retrieves data without modifying state.
Register the pfSense Enhanced MCP Server MCP server in PolicyLayer and add a rule for find_blocked_rules: 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 Enhanced MCP Server. Nothing to install.
find_blocked_rules is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the find_blocked_rules 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 find_blocked_rules. 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.
find_blocked_rules is provided by the pfSense Enhanced MCP Server MCP server (mmaxwellcb/pfsesen_mcp_2). 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 →