pfsense_get_user_auth_server

GET /api/v2/user/auth_server

SERVERPfsense SOURCEabl030/pfsense-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/abl030-pfsense-mcp/pfsense-get-user-auth-server.md

WHAT IT DOES

What pfsense_get_user_auth_server does on Pfsense

AI agents call pfsense_get_user_auth_server 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.

RISK

Why pfsense_get_user_auth_server is rated Low

This tool retrieves authentication server configuration from pfSense. While it is a read-only operation, the sensitivity is elevated to medium severity because authentication server details could include connection parameters, credentials hints, or configuration that could enable lateral attacks or compromise of authentication mechanisms.

From the tool's definition Tool name contains 'get' and description shows GET HTTP method (/api/v2/user/auth_server), indicating data retrieval with no modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pfsense_get_user_auth_server 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_get_user_auth_server, this is the rule to start with:

pfsense_get_user_auth_server Allowed

pfsense_get_user_auth_server is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pfsense, apply this rule, and every pfsense_get_user_auth_server call is checked against it from then on.

FAQ

Questions about pfsense_get_user_auth_server

What does the pfsense_get_user_auth_server tool do? +

GET /api/v2/user/auth_server. It is categorised as a Read tool in the Pfsense MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pfsense_get_user_auth_server? +

Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_get_user_auth_server: 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.

What risk level is pfsense_get_user_auth_server? +

pfsense_get_user_auth_server is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pfsense_get_user_auth_server? +

Yes. Add a rate_limit block to the pfsense_get_user_auth_server 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.

How do I block pfsense_get_user_auth_server completely? +

Set action: deny in the PolicyLayer policy for pfsense_get_user_auth_server. 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.

What MCP server provides pfsense_get_user_auth_server? +

pfsense_get_user_auth_server 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.

KEEP EXPLORING

More on Pfsense, and thousands of servers like it.

This server

All 680 Pfsense tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →