Return the current scene tracked by this MCP session, if one was opened
AI agents call scene_get_current to retrieve information from Godot Devtool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward getter that retrieves state information about the currently active scene in the Godot development session. It performs no mutations, executions, or destructive actions. The blast radius of misuse is minimal—an AI agent could only learn what scene is open, which is informational. Classified as Read with low severity.
From the tool's definition Tool name and description indicate retrieval only: 'Return the current scene tracked by this MCP session'. No modification, deletion, or execution of code occurs. The verb 'Return' and passive tracking imply a query operation with no side effects.
Documented attack patterns abuse exactly the kind of access scene_get_current gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for scene_get_current:
{
"version": "1",
"default": "deny",
"tools": {
"scene_get_current": {}
}
}scene_get_current is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Return the current scene tracked by this MCP session, if one was opened. It is categorised as a Read tool in the Godot Devtool MCP Server, which means it retrieves data without modifying state.
Register the Godot Devtool MCP server in PolicyLayer and add a rule for scene_get_current: 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 Devtool. Nothing to install.
scene_get_current 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 scene_get_current 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 scene_get_current. 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.
scene_get_current is provided by the Godot Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.