pfsense_replace_services_free_radius_interfaces
PUT /api/v2/services/freeradius/interfaces
This record as markdown: /tools/abl030-pfsense-mcp/pfsense-replace-services-free-radius-interfaces.md
What pfsense_replace_services_free_radius_interfaces does on Pfsense
AI agents use pfsense_replace_services_free_radius_interfaces 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_replace_services_free_radius_interfaces is rated Medium
This tool modifies firewall service configuration reversibly via a PUT request. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial). However, the severity is high because misconfiguring RADIUS interfaces can compromise authentication infrastructure, disable user access, or create security vulnerabilities in the firewall's identity management system.
From the tool's definition PUT /api/v2/services/freeradius/interfaces — a PUT operation that modifies service configuration (FreeRADIUS interfaces).
Attacks that exploit this kind of access
The rule that runs pfsense_replace_services_free_radius_interfaces 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_replace_services_free_radius_interfaces, this is the rule to start with:
pfsense_replace_services_free_radius_interfaces stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Pfsense, apply this rule, and every pfsense_replace_services_free_radius_interfaces call is checked against it from then on.
Questions about pfsense_replace_services_free_radius_interfaces
PUT /api/v2/services/freeradius/interfaces. 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.
Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_replace_services_free_radius_interfaces: 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_replace_services_free_radius_interfaces is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pfsense_replace_services_free_radius_interfaces 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_replace_services_free_radius_interfaces. 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_replace_services_free_radius_interfaces 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.
More on Pfsense, and thousands of servers like it.
This server
Across the catalogue