pfsense_create_firewall_traffic_shaper_limiter
A write tool on the Pfsense MCP server.
This record as markdown: /tools/abl030-pfsense-mcp/pfsense-create-firewall-traffic-shaper-limiter.md
What pfsense_create_firewall_traffic_shaper_limiter does on Pfsense
AI agents use pfsense_create_firewall_traffic_shaper_limiter 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_firewall_traffic_shaper_limiter is rated Medium
This tool creates traffic shaper limiter configurations on pfSense firewalls. While the description is empty, the 'create' verb and context of firewall configuration management indicate it modifies network policy settings reversibly. This is Write-category (configuration change) rather than Destructive (no deletion), Execute (no code execution), or Read (performs modification).
From the tool's definition Tool name contains 'create' indicating data creation; server description states it gives 'full control over pfSense firewalls via REST API v2' with tools covering 'traffic shaper' configuration.
Attacks that exploit this kind of access
The rule that runs pfsense_create_firewall_traffic_shaper_limiter 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_create_firewall_traffic_shaper_limiter, this is the rule to start with:
pfsense_create_firewall_traffic_shaper_limiter 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_create_firewall_traffic_shaper_limiter call is checked against it from then on.
Questions about pfsense_create_firewall_traffic_shaper_limiter
pfsense_create_firewall_traffic_shaper_limiter 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_create_firewall_traffic_shaper_limiter: 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_create_firewall_traffic_shaper_limiter 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_create_firewall_traffic_shaper_limiter 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_create_firewall_traffic_shaper_limiter. 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_create_firewall_traffic_shaper_limiter 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