AI agents invoke pt_send_raw to trigger actions in Packet Tracer MCP. 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.
The name 'pt_send_raw' strongly implies sending raw data or commands, likely raw CLI commands or packets to a Cisco Packet Tracer device. In the context of a network simulation/configuration server with sibling tools like pt_apply_acl, pt_deploy, and pt_delete_device, a 'send_raw' tool most plausibly executes arbitrary raw CLI commands or configurations against network devices.
From the tool's definition Tool name 'pt_send_raw' — description is empty and uninformative
Documented attack patterns abuse exactly the kind of access pt_send_raw 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_send_raw:
{
"version": "1",
"default": "deny",
"tools": {
"pt_send_raw": {
"limits": [
{
"counter": "pt_send_raw_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} pt_send_raw stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
pt_send_raw. It is categorised as a Execute tool in the Packet Tracer MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Packet Tracer MCP server in PolicyLayer and add a rule for pt_send_raw: 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_send_raw 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 pt_send_raw 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_send_raw. 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_send_raw 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.