Exporta el plan a archivos: script JS, configs CLI y JSON.
AI agents use pt_export 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.
The tool creates and writes multiple file outputs (JavaScript scripts, CLI configuration files, JSON data) based on network topology plans. This is a Write operation because it generates and stores new data artifacts. The severity is medium because exported configuration files could contain sensitive network details or scripts that, if misused, could lead to misconfiguration, though the export itself is reversible.
From the tool's definition Tool exports/generates output files in multiple formats (JS script, CLI configs, JSON). Description states 'Exporta el plan a archivos' (exports the plan to files), which creates or generates data artifacts that are written to the system.
Documented attack patterns abuse exactly the kind of access pt_export 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_export:
{
"version": "1",
"default": "deny",
"tools": {
"pt_export": {
"limits": [
{
"counter": "pt_export_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}pt_export 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.
Exporta el plan a archivos: script JS, configs CLI y JSON. 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_export: 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_export 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_export 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_export. 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_export 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.