get_status

System status / diagnostics: editor bridge, live-game runtime bridge, and tool count. Use to debug connection issues.

SERVERGodot SOURCE@yanhuifair/godot-mcp

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yanhuifair-godot-mcp/get-status.md

WHAT IT DOES

What get_status does on Godot

AI agents call get_status to retrieve information from Godot 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
`probe_runtime`	object	—	Also probe the live-game runtime bridge (port 9877).

Parameters from the server's own tool schema.

RISK

Why get_status is rated Low

Retrieves diagnostic information about runtime and editor status without side effects.

From the tool's definition System status, diagnostics, editor bridge, tool count

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_status safely

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

get_status Allowed

get_status 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": {
    "get_status": {}
  }
}

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

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

FAQ

Questions about get_status

What does the get_status tool do? +

System status / diagnostics: editor bridge, live-game runtime bridge, and tool count. Use to debug connection issues. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.

What parameters does get_status accept? +

get_status accepts 1 parameter: probe_runtime. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_status? +

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

What risk level is get_status? +

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

Can I rate-limit get_status? +

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

How do I block get_status completely? +

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

What MCP server provides get_status? +

get_status 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.

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 386 Godot tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →editor_status on 010 Editor →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server → The MCP Attack Database →

Guides

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