Retrieve network requests (XHR, fetch, navigation, static assets) from a circular buffer. Use when the user wants to debug API calls, check request/response status codes, monitor network activity, or verify that a request was made after an action. Parameters: - clear: Set to true to clear the buf...
AI agents call pilot_network to retrieve information from Pilot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads/retrieves already-captured network request data from an internal buffer. It does not trigger any network requests, execute code, or modify any state (the optional clear flag only empties the local buffer). It is purely observational/diagnostic.
From the tool's definition Retrieve network requests (XHR, fetch, navigation, static assets) from a circular buffer
Documented attack patterns abuse exactly the kind of access pilot_network gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pilot, and nothing reaches the server without passing your rules. This is the rule we recommend for pilot_network:
{
"version": "1",
"default": "deny",
"tools": {
"pilot_network": {}
}
}pilot_network is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve network requests (XHR, fetch, navigation, static assets) from a circular buffer. Use when the user wants to debug API calls, check request/response status codes, monitor network activity, or verify that a request was made after an action. Parameters: - clear: Set to true to clear the buffer after reading (useful for isolating new requests after an action) Returns: List of requests showing method, URL, status code, duration in ms, and response size in bytes. Or. It is categorised as a Read tool in the Pilot MCP Server, which means it retrieves data without modifying state.
Register the Pilot MCP server in PolicyLayer and add a rule for pilot_network: 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 Pilot. Nothing to install.
pilot_network 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 pilot_network 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 pilot_network. 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.
pilot_network is provided by the Pilot MCP server (tacosyhorchata/pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 61 Pilot tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
61 Pilot tools catalogued and risk-classified — across an index of 42,500+ MCP servers.