pfsense_create_services_free_radius_user

pfsense_create_services_free_radius_user

Server Pfsense abl030/pfsense-mcp
Category Write
Risk class Medium
Parameters 00 required

What pfsense_create_services_free_radius_user does on Pfsense

AI agents use pfsense_create_services_free_radius_user to create or update resources in Pfsense — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pfsense environment.

Why pfsense_create_services_free_radius_user needs a policy

Creating a RADIUS user is a write operation—it adds a new authentication credential to the system. The action is reversible (the user can be deleted), so it does not qualify as Destructive. However, it directly modifies authentication infrastructure on a critical network device (pfSense firewall), making unauthorized or malicious user creation a significant security risk.

From the tool's definition Tool name contains 'create' and 'user', indicating it creates a new RADIUS user account on a pfSense firewall.

Questions about pfsense_create_services_free_radius_user

What does the pfsense_create_services_free_radius_user tool do? +

pfsense_create_services_free_radius_user. It is categorised as a Write tool in the Pfsense MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pfsense_create_services_free_radius_user? +

Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_create_services_free_radius_user: 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_create_services_free_radius_user? +

pfsense_create_services_free_radius_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pfsense_create_services_free_radius_user? +

Yes. Add a rate_limit block to the pfsense_create_services_free_radius_user 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_create_services_free_radius_user completely? +

Set action: deny in the PolicyLayer policy for pfsense_create_services_free_radius_user. 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_create_services_free_radius_user? +

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.