pfsense_list_firewall_traffic_shaper_queues

pfsense_list_firewall_traffic_shaper_queues

Server Pfsense abl030/pfsense-mcp
Category Read
Risk class Low
Parameters 00 required

What pfsense_list_firewall_traffic_shaper_queues does on Pfsense

AI agents call pfsense_list_firewall_traffic_shaper_queues to retrieve information from Pfsense without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why pfsense_list_firewall_traffic_shaper_queues needs a policy

This tool retrieves or enumerates traffic shaper queues from pfSense, which is a read-only operation. It does not modify, delete, or execute operations on the firewall. While the empty description is uninformative, the 'list' verb in the tool name strongly indicates a Read category action that queries existing configuration data without causing side effects.

From the tool's definition Tool name is 'pfsense_list_firewall_traffic_shaper_queues' - the verb 'list' indicates data retrieval with no side effects. The description is empty, which slightly reduces confidence, but the naming convention clearly indicates a query operation.

Questions about pfsense_list_firewall_traffic_shaper_queues

What does the pfsense_list_firewall_traffic_shaper_queues tool do? +

pfsense_list_firewall_traffic_shaper_queues. 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_list_firewall_traffic_shaper_queues? +

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

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

Can I rate-limit pfsense_list_firewall_traffic_shaper_queues? +

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

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

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