Get captured logpoint hits from console API calls (paginated: omit offset/limit to return everything; default offset=0)
AI agents call getLogpointHits to retrieve information from MCP Chrome Debugger Protocol without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves debugging information (logpoint hits/console output) from a running process without modifying state, executing code, or affecting the debugged application. It is purely observational, fitting the Read category with low severity since it only exposes debug logs.
From the tool's definition Tool name 'getLogpointHits' and description 'Get captured logpoint hits from console API calls' indicate data retrieval. The pagination parameters (offset/limit) and retrieval-only semantics confirm no side effects or modifications.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get captured logpoint hits from console API calls (paginated: omit offset/limit to return everything; default offset=0). It is categorised as a Read tool in the MCP Chrome Debugger Protocol MCP Server, which means it retrieves data without modifying state.
Register the MCP Chrome Debugger Protocol MCP server in PolicyLayer and add a rule for getLogpointHits: 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 MCP Chrome Debugger Protocol. Nothing to install.
getLogpointHits 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 getLogpointHits 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 getLogpointHits. 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.
getLogpointHits is provided by the MCP Chrome Debugger Protocol MCP server (vitalyostanin/mcp-chrome-debugger-protocol). 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 →