take_screenshot
Capture a screenshot of the active editor viewport. Returns the file path of the saved image.
This record as markdown: /tools/jjpxdev-unreal-mcp/take-screenshot.md
What take_screenshot does on Unreal
AI agents call take_screenshot to retrieve information from Unreal 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 |
|---|---|---|---|
filename | string | — | Output filename (default: screenshot_<timestamp>.png) |
Parameters from the server's own tool schema.
Why take_screenshot is rated Low
This is a read operation that queries visual state from the Unreal Editor viewport without side effects. It does not modify assets, execute code, delete data, or trigger game mechanics. The captured image is a new file created as output, but this is a standard artifact of the read operation, not a write of meaningful game state.
From the tool's definition The tool 'take_screenshot' captures a screenshot of the editor viewport and returns a file path. The description explicitly states it 'Capture[s] a screenshot' with no modification, deletion, or execution of game logic—it only retrieves visual data from the…
Risk signalsAccepts file system path (filename)
Attacks that exploit this kind of access
The rule that runs take_screenshot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For take_screenshot, this is the rule to start with:
take_screenshot 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 Unreal, apply this rule, and every take_screenshot call is checked against it from then on.
Questions about take_screenshot
Capture a screenshot of the active editor viewport. Returns the file path of the saved image. It is categorised as a Read tool in the Unreal MCP Server, which means it retrieves data without modifying state.
take_screenshot accepts 1 parameter: filename. The full parameter table on this page comes from the server's own tool schema.
Register the Unreal MCP server in PolicyLayer and add a rule for take_screenshot: 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 Unreal. Nothing to install.
take_screenshot 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 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. 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 is provided by the Unreal MCP server (@jjpxdev/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unreal, and thousands of servers like it.
This server
Across the catalogue