AI agents call traceroute to retrieve information from Kali without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Traceroute is a passive network diagnostic tool that sends probe packets to discover the route to a destination host. It reads/observes network topology without modifying any data or systems. However, it does generate network traffic and could be used for reconnaissance in a pentest context.
From the tool's definition Trace the network path to a host
Attacks that exploit this kind of access
Trace the network path to a host. It is categorised as a Read tool in the Kali MCP Server, which means it retrieves data without modifying state.
Register the Kali MCP server in PolicyLayer and add a rule for traceroute: 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 Kali. Nothing to install.
traceroute is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the traceroute 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 traceroute. 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.
traceroute is provided by the Kali MCP server (rangta10/kali-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 →