Retrieve browser console messages (console.log, console.warn, console.error) from a circular buffer. Use when the user wants to debug JavaScript errors, check application logs, inspect warnings, or see what the page is printing to the console. Parameters: - level: Filter messages by log level —
AI agents call pilot_console 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 is a diagnostic/observational tool that retrieves existing console output without side effects. It neither executes code nor modifies state—it only reads logs already present in the browser's console buffer. The tool is passive introspection, consistent with the Read category (retrieves or queries data; no side effects).
From the tool's definition Tool description explicitly states "Retrieve browser console messages" with no modification, deletion, or execution capabilities. Parameters limited to filtering by log level. Reads from circular buffer only.
Documented attack patterns abuse exactly the kind of access pilot_console 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_console:
{
"version": "1",
"default": "deny",
"tools": {
"pilot_console": {}
}
}pilot_console 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 browser console messages (console.log, console.warn, console.error) from a circular buffer. Use when the user wants to debug JavaScript errors, check application logs, inspect warnings, or see what the page is printing to the console. Parameters: - level: Filter messages by log level —. 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_console: 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_console 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_console 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_console. 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_console 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.