Get the current debug state including steps, logs, and screenshots
AI agents call get_debug_state to retrieve information from AutoSpectra 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 and queries existing debug state data with no side effects, no data modification, and no external operations. It falls squarely into the Read category. The severity is low because debug logs and screenshots are typically non-sensitive diagnostic outputs that do not impact production systems or user data when exposed.
From the tool's definition Tool description states 'Get the current debug state' — the verb 'Get' indicates retrieval without modification. The listed outputs (steps, logs, screenshots) are read-only diagnostic information.
Attacks that exploit this kind of access
Get the current debug state including steps, logs, and screenshots. It is categorised as a Read tool in the AutoSpectra MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AutoSpectra MCP Server MCP server in PolicyLayer and add a rule for get_debug_state: 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 AutoSpectra MCP Server. Nothing to install.
get_debug_state 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_debug_state 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_debug_state. 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_debug_state is provided by the AutoSpectra MCP Server MCP server (raphaenterprises-ai/autospectra-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_debug_state is one line of AutoSpectra MCP Server'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 →