Extract console logs from Chrome browser tabs using Chrome DevTools Protocol. Can extract from current tab or navigate to a URL first. Captures console.log/error/warn, runtime exceptions, and network failures including CORS errors. Returns structured log data with timestamps, sources, and stack t...
AI agents call pilotgentic_extract_console_logs to retrieve information from PilotGentic without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reads and retrieves console logs from a browser's DevTools Protocol, which is a passive observation action with no side effects on the system or browser state. However, severity is elevated from 'low' to 'medium' because console logs may contain sensitive information (API keys, tokens, personal data, error messages revealing system architecture) that could be exfiltrated by a misbehaving agent, and the tool…
From the tool's definition Tool description states it 'Extract[s] console logs' and 'Captures console.log/error/warn, runtime exceptions, and network failures' — the verb is 'extract' and 'capture', indicating data retrieval only.
Attacks that exploit this kind of access
Extract console logs from Chrome browser tabs using Chrome DevTools Protocol. Can extract from current tab or navigate to a URL first. Captures console.log/error/warn, runtime exceptions, and network failures including CORS errors. Returns structured log data with timestamps, sources, and stack traces. It is categorised as a Read tool in the PilotGentic MCP Server, which means it retrieves data without modifying state.
Register the PilotGentic MCP server in PolicyLayer and add a rule for pilotgentic_extract_console_logs: 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 PilotGentic. Nothing to install.
pilotgentic_extract_console_logs 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 pilotgentic_extract_console_logs 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 pilotgentic_extract_console_logs. 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.
pilotgentic_extract_console_logs is provided by the PilotGentic MCP server (@pilotgentic/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
pilotgentic_extract_console_logs is one line of PilotGentic's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →