pfsense_update_routing_gateway_group_priority
A write tool on the Pfsense MCP server.
This record as markdown: /tools/abl030-pfsense-mcp/pfsense-update-routing-gateway-group-priority.md
What pfsense_update_routing_gateway_group_priority does on Pfsense
AI agents use pfsense_update_routing_gateway_group_priority 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_update_routing_gateway_group_priority is rated Medium
This tool modifies routing gateway group priority settings, which is a reversible configuration change to network routing behavior. It does not delete data (Destructive), execute arbitrary code (Execute), or involve financial transactions (Financial). While the description is empty, the naming convention and server context indicate it updates routing configuration.
From the tool's definition Tool name includes 'update' and targets 'routing_gateway_group_priority' on a pfSense firewall REST API server with 677 tools covering firewall rules, NAT, VPN, services, routing, certificates, users, and diagnostics.
Attacks that exploit this kind of access
The rule that runs pfsense_update_routing_gateway_group_priority 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_update_routing_gateway_group_priority, this is the rule to start with:
pfsense_update_routing_gateway_group_priority 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_update_routing_gateway_group_priority call is checked against it from then on.
Questions about pfsense_update_routing_gateway_group_priority
pfsense_update_routing_gateway_group_priority is a write tool on the Pfsense MCP server. 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_update_routing_gateway_group_priority: 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_update_routing_gateway_group_priority 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_update_routing_gateway_group_priority 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_update_routing_gateway_group_priority. 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_update_routing_gateway_group_priority 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