Comprehensive debugging information for window detection issues.
AI agents call debug_window_detection to retrieve information from Auto-Snap MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves diagnostic information about window detection without modifying, executing, or deleting any data. It is purely informational for debugging window detection problems, making it a Read operation with low severity since it only exposes diagnostic data that aids in troubleshooting the screenshot/document processing workflow.
From the tool's definition Tool name 'debug_window_detection' and description 'Comprehensive debugging information for window detection issues' indicate retrieval and inspection of system state for troubleshooting purposes.
Attacks that exploit this kind of access
Comprehensive debugging information for window detection issues. It is categorised as a Read tool in the Auto-Snap MCP MCP Server, which means it retrieves data without modifying state.
Register the Auto-Snap MCP server in PolicyLayer and add a rule for debug_window_detection: 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 Auto-Snap MCP. Nothing to install.
debug_window_detection 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 debug_window_detection 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 debug_window_detection. 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.
debug_window_detection is provided by the Auto-Snap MCP server (povedaaqui/auto-snap-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 →