AI agents call pfsense_get_interface_gre to retrieve information from Pfsense without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves GRE (Generic Routing Encapsulation) interface information from a pfSense firewall. As a GET endpoint, it only queries and returns data without side effects. Although the server overall provides extensive firewall control capabilities, this specific tool is limited to read-only data retrieval.
From the tool's definition Tool name contains 'get' and description shows 'GET' HTTP method to retrieve interface GRE configuration via REST API. No modification, deletion, or execution of operations occurs.
Attacks that exploit this kind of access
GET /api/v2/interface/gre. It is categorised as a Read tool in the Pfsense MCP Server, which means it retrieves data without modifying state.
Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_get_interface_gre: 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_get_interface_gre 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 pfsense_get_interface_gre 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_get_interface_gre. 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_get_interface_gre 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 →