Get console logs from a browser target. Starts monitoring on first call.
AI agents call get_console_logs to retrieve information from Simple Console MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves console log data from a browser session for debugging purposes. It performs passive monitoring and data collection without creating, modifying, deleting, or executing any operations. While it may have the minor side effect of initiating monitoring on first call, this is a benign initialization activity.
From the tool's definition Tool description states it 'Get console logs from a browser target' and 'Starts monitoring on first call.' The verb 'get' and function of retrieving/monitoring logs indicate read-only data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get console logs from a browser target. Starts monitoring on first call. It is categorised as a Read tool in the Simple Console MCP MCP Server, which means it retrieves data without modifying state.
Register the Simple Console MCP server in PolicyLayer and add a rule for get_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 Simple Console MCP. Nothing to install.
get_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 get_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 get_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.
get_console_logs is provided by the Simple Console MCP server (tznthou/simple-console-mcp). 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 →