AI agents use pt_add_module to create or update resources in Packet Tracer MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Packet Tracer MCP environment.
Adding modules to a network topology creates or modifies configuration reversibly—typical Write category behavior. Lacks the irreversibility of Destructive (no delete/drop semantics) and doesn't execute arbitrary commands like Execute category tools. Severity is medium because misconfigured modules could disrupt network simulations but changes are reversible and scoped to a lab environment.
From the tool's definition Tool name 'pt_add_module' indicates adding/modifying network modules in Cisco Packet Tracer; server description states it 'allows LLMs to create, configure...topologies.' Empty tool description lowers confidence but context suggests configuration capability.
Documented attack patterns abuse exactly the kind of access pt_add_module gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Packet Tracer MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for pt_add_module:
{
"version": "1",
"default": "deny",
"tools": {
"pt_add_module": {
"limits": [
{
"counter": "pt_add_module_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}pt_add_module 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.
Free to start. No card required.
pt_add_module. It is categorised as a Write tool in the Packet Tracer MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Packet Tracer MCP server in PolicyLayer and add a rule for pt_add_module: 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 Packet Tracer MCP. Nothing to install.
pt_add_module 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 pt_add_module 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 pt_add_module. 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.
pt_add_module is provided by the Packet Tracer MCP server (mats2208/mcp-packet-tracer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Packet Tracer MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
33 Packet Tracer MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.