runtime_get_log

Read the runtime log ring buffer (entries game code pushed via BreakpointRuntimeBridge.push_log).

SERVERGodot Breakpoint SOURCEjlivingston-Cipher/godot-breakpoint-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/godot-breakpoint-mcp/runtime-get-log.md

WHAT IT DOES

What runtime_get_log does on Godot Breakpoint

AI agents call runtime_get_log to retrieve information from Godot Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why runtime_get_log is rated Low

This tool retrieves log entries from a ring buffer that game code has already pushed. It performs a read-only query of existing data with no capability to modify, delete, or execute operations. The blast radius is minimal—at worst, an agent could read debug logs, which poses no security or functional risk to the Godot editor or game.

From the tool's definition Tool name includes 'get', description states 'Read the runtime log ring buffer' with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs runtime_get_log safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For runtime_get_log, this is the rule to start with:

runtime_get_log Allowed

runtime_get_log is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "runtime_get_log": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot Breakpoint, apply this rule, and every runtime_get_log call is checked against it from then on.

FAQ

Questions about runtime_get_log

What does the runtime_get_log tool do? +

Read the runtime log ring buffer (entries game code pushed via BreakpointRuntimeBridge.push_log). It is categorised as a Read tool in the Godot Breakpoint MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on runtime_get_log? +

Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for runtime_get_log: 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 Breakpoint. Nothing to install.

What risk level is runtime_get_log? +

runtime_get_log is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit runtime_get_log? +

Yes. Add a rate_limit block to the runtime_get_log 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.

How do I block runtime_get_log completely? +

Set action: deny in the PolicyLayer policy for runtime_get_log. 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.

What MCP server provides runtime_get_log? +

runtime_get_log is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Godot Breakpoint, and thousands of servers like it.

This server

All 239 Godot Breakpoint tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →