editor_get_recent_scenes

List recently opened scene paths.

SERVERGodot SOURCE@yanhuifair/godot-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/yanhuifair-godot-mcp/editor-get-recent-scenes.md

WHAT IT DOES

What editor_get_recent_scenes does on Godot

AI agents call editor_get_recent_scenes 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.

RISK

Why editor_get_recent_scenes is rated Low

This tool retrieves historical metadata about recently opened scenes from the Godot editor state. It performs a read-only query that returns information without modifying any data, creating, executing commands, or altering the system state. The scope is limited to editor session history, making it low severity.

From the tool's definition Tool name 'editor_get_recent_scenes' and description 'List recently opened scene paths' indicate a retrieval/query operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs editor_get_recent_scenes 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 editor_get_recent_scenes, this is the rule to start with:

editor_get_recent_scenes Allowed

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

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 editor_get_recent_scenes call is checked against it from then on.

FAQ

Questions about editor_get_recent_scenes

What does the editor_get_recent_scenes tool do? +

List recently opened scene paths. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on editor_get_recent_scenes? +

Register the Godot MCP server in PolicyLayer and add a rule for editor_get_recent_scenes: 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 editor_get_recent_scenes? +

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

Can I rate-limit editor_get_recent_scenes? +

Yes. Add a rate_limit block to the editor_get_recent_scenes 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 editor_get_recent_scenes completely? +

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

editor_get_recent_scenes 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 282 Godot 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 →