Get the current status of the debug stream WebSocket server
AI agents call get_debug_stream_status to retrieve information from Godot MCP Unified without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves information about the debug stream WebSocket server's current state. It does not modify, execute, delete, or transfer resources. The operation is read-only and non-destructive, making it the lowest risk category.
From the tool's definition Tool name is 'get_debug_stream_status' and description states it 'Get[s] the current status of the debug stream WebSocket server' — a pure status query with no side effects.
Attacks that exploit this kind of access
Get the current status of the debug stream WebSocket server. It is categorised as a Read tool in the Godot MCP Unified MCP Server, which means it retrieves data without modifying state.
Register the Godot MCP Unified MCP server in PolicyLayer and add a rule for get_debug_stream_status: 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 Godot MCP Unified. Nothing to install.
get_debug_stream_status 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_stream_status 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_stream_status. 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_stream_status is provided by the Godot MCP Unified MCP server (pierrealexandreguillemin-a11y/godot-mcp-unified). 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 →