godot_output
Read captured console output for a managed process (from godot_run_managed). Use since_seq for incremental reads.
This record as markdown: /tools/breakpoint-mcp/godot-output.md
What godot_output does on Breakpoint
AI agents call godot_output to retrieve information from Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Process id from godot_run_managed |
stream | string | — | Filter by stream (default both) |
since_seq | integer | — | Only lines with seq greater than this (default 0) |
Parameters from the server's own tool schema.
Why godot_output is rated Low
This tool retrieves console output from a managed process—a query operation with no capability to modify, execute, delete, or move data. It is purely informational, making it a Read category tool with low severity since console output is typically non-sensitive diagnostic information.
From the tool's definition Tool description explicitly states 'Read captured console output' and mentions 'incremental reads', indicating retrieval of data with no side effects.
Attacks that exploit this kind of access
The rule that runs godot_output safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For godot_output, this is the rule to start with:
godot_output is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every godot_output call is checked against it from then on.
Questions about godot_output
Read captured console output for a managed process (from godot_run_managed). Use since_seq for incremental reads. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
godot_output accepts 3 parameters: id, stream, since_seq. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for godot_output: 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 Breakpoint. Nothing to install.
godot_output 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 godot_output 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 godot_output. 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.
godot_output is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue