Manage traffic shaping rules on PE routers using the trafficshaper CLI tool. Supports setting delays, showing rules, deleting rules, and other traffic impairment operations.
AI agents invoke trafficshaper to trigger actions in Linux MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes CLI commands on PE (Provider Edge) routers to manipulate network traffic shaping rules. While it includes 'deleting rules' (which could be Destructive), the primary nature is executing network operations that alter traffic behavior. Misuse could cause widespread network outages or impairment across customer traffic on PE routers, justifying high severity.
From the tool's definition 'Manage traffic shaping rules on PE routers using the trafficshaper CLI tool. Supports setting delays, showing rules, deleting rules, and other traffic impairment operations.'
Attacks that exploit this kind of access
Manage traffic shaping rules on PE routers using the trafficshaper CLI tool. Supports setting delays, showing rules, deleting rules, and other traffic impairment operations. It is categorised as a Execute tool in the Linux MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Linux MCP Server MCP server in PolicyLayer and add a rule for trafficshaper: 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 Linux MCP Server. Nothing to install.
trafficshaper is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the trafficshaper 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 trafficshaper. 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.
trafficshaper is provided by the Linux MCP Server MCP server (jnprautomate/linux-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →