AI agents call pfsense_list_vpn_openvpn_csos 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 name strongly suggests it lists VPN OpenVPN client-server OpenVPN settings (CSOs likely refers to Client-Server OpenVPN). Listing operations are Read-category as they retrieve data without side effects. However, the empty description and the sensitive nature of VPN configuration data (which could be leveraged for reconnaissance or to inform network attacks) elevates severity to medium rather than low.
From the tool's definition Tool name 'pfsense_list_vpn_openvpn_csos' contains 'list', indicating a retrieval operation. The 'list' verb is characteristic of Read operations that query data without modification. Description is empty, reducing confidence.
Attacks that exploit this kind of access
pfsense_list_vpn_openvpn_csos. 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_openvpn_csos: 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_openvpn_csos 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_openvpn_csos 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_openvpn_csos. 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_openvpn_csos 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 →