AI agents call monitor_output to retrieve information from Godot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
clear | object | — | Clear accumulated output after reading |
Parameters from the server's own tool schema.
This tool queries or retrieves process output from the Godot engine—a read-only operation with no side effects. It fits the Read category (retrieves data; no side effects). The severity is low because process output typically contains non-sensitive diagnostic information and poses minimal risk even if accessed by an AI agent.
From the tool's definition Tool name 'monitor_output' and description 'Read Godot process output' indicate retrieval of diagnostic/logging data without modification or execution.
Attacks that exploit this kind of access
Read Godot process output. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
monitor_output accepts 1 parameter: clear. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for monitor_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 Godot. Nothing to install.
monitor_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 monitor_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 monitor_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.
monitor_output is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
monitor_output is one line of Godot'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 →