get_scene_info
AI agents call get_scene_info to retrieve information from GameDevBench MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about a game scene in Godot, which is a read-only operation with no side effects. The name pattern follows query/get semantics typical of Read category tools. The empty description limits confidence slightly, but context from the server's purpose (capturing and visualizing runtime state) supports classification as data retrieval rather than code execution or state modification.
From the tool's definition Tool name 'get_scene_info' indicates retrieval of scene information from Godot runtime. No description provided, but the name and server context (visualization of runtime behavior for benchmarking) suggest querying/inspection of game state rather than…
Attacks that exploit this kind of access
get_scene_info. It is categorised as a Read tool in the GameDevBench MCP MCP Server, which means it retrieves data without modifying state.
Register the GameDevBench MCP server in PolicyLayer and add a rule for get_scene_info: 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 GameDevBench MCP. Nothing to install.
get_scene_info 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 get_scene_info 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 get_scene_info. 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.
get_scene_info is provided by the GameDevBench MCP server (seeleai/gamedevbench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →