pfsense_list_status_openvpn_server_routes

What pfsense_list_status_openvpn_server_routes does on Pfsense

AI agents call pfsense_list_status_openvpn_server_routes to retrieve information from Pfsense without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why pfsense_list_status_openvpn_server_routes is rated Low

The 'list_' prefix and context of querying 'status' of OpenVPN routes indicates this is a Read operation that retrieves configuration or state information without side effects. While the description is empty, the naming convention is sufficiently clear. Severity is low because reading firewall status information poses minimal risk compared to tools that modify rules, create routes, or execute commands.

From the tool's definition Tool name begins with 'pfsense_list_' indicating a query/retrieval operation on OpenVPN server routes status. No modification, execution, or destructive operation is implied by the 'list' prefix.

The rule that runs pfsense_list_status_openvpn_server_routes safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pfsense, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pfsense_list_status_openvpn_server_routes, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pfsense_list_status_openvpn_server_routes": {}
  }
}

Questions about pfsense_list_status_openvpn_server_routes