AI agents call pfsense_list_vpn_wireguard_tunnels 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.
The tool retrieves or queries WireGuard VPN tunnel information from a pfSense firewall. While this is a Read operation (no data modification), severity is elevated to 'high' because: (1) VPN tunnels are security-critical infrastructure, (2) tunnel configuration details could reveal network topology and security posture, (3) this server controls firewalls with 677 tools spanning all security functions, so exposure…
From the tool's definition Tool name 'pfsense_list_vpn_wireguard_tunnels' indicates a list/query operation that retrieves VPN tunnel data without modifying it. The 'list' verb is characteristic of Read operations. Description is empty, limiting confidence slightly.
Attacks that exploit this kind of access
pfsense_list_vpn_wireguard_tunnels. 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_list_vpn_wireguard_tunnels: 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_list_vpn_wireguard_tunnels 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_list_vpn_wireguard_tunnels 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_list_vpn_wireguard_tunnels. 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_list_vpn_wireguard_tunnels 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 →