take_screenshot_with_context
Take a screenshot with scene context metadata (node tree, properties of specified nodes)
This record as markdown: /tools/keeveeg-godot-mcp/take-screenshot-with-context.md
What take_screenshot_with_context does on Godot
AI agents call take_screenshot_with_context 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 |
|---|---|---|---|
name | string | Yes | Name for this screenshot (used as filename, e.g. "main_menu") |
include_nodes | array | — | Node paths to include property data for (requires include_props=true) |
include_props | boolean | — | Whether to include property snapshots for listed include_nodes (default: false) |
Parameters from the server's own tool schema.
Why take_screenshot_with_context is rated Low
Screenshots and metadata queries are read-only operations that inspect the current state of the Godot editor/scene without creating, modifying, deleting, or executing operations. The tool's purpose is passive observation, not action. Severity is low as misuse would only expose scene information without affecting the project itself.
From the tool's definition The tool 'take_screenshot_with_context' performs a screenshot capture and retrieves 'scene context metadata (node tree, properties of specified nodes)' — this is data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs take_screenshot_with_context 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 take_screenshot_with_context, this is the rule to start with:
take_screenshot_with_context is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every take_screenshot_with_context call is checked against it from then on.
Questions about take_screenshot_with_context
Take a screenshot with scene context metadata (node tree, properties of specified nodes). It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
take_screenshot_with_context accepts 3 parameters: name, include_nodes, include_props. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for take_screenshot_with_context: 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.
take_screenshot_with_context 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 take_screenshot_with_context 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 take_screenshot_with_context. 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.
take_screenshot_with_context is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue