Get captured console messages (log, warn, error, info)
AI agents call console_get_logs to retrieve information from CDP-MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves console output (log, warn, error, info messages) from a browser debugging session without modifying state, executing code, or affecting external systems. It is a read-only diagnostic operation with minimal blast radius. An AI agent misusing this tool could only access information already logged to the console, posing no irreversible harm, financial risk, or system compromise.
From the tool's definition Tool name 'console_get_logs' and description 'Get captured console messages' indicate data retrieval with no modification or side effects. The action is purely observational—reading already-captured logs.
Attacks that exploit this kind of access
Get captured console messages (log, warn, error, info). It is categorised as a Read tool in the CDP-MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CDP-MCP Server MCP server in PolicyLayer and add a rule for console_get_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 CDP-MCP Server. Nothing to install.
console_get_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 console_get_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 console_get_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.
console_get_logs is provided by the CDP-MCP Server MCP server (jekyll-001/cdp-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 →