This record as markdown: /tools/jjpxdev-unreal-mcp/get-undo-history.md
What get_undo_history does on Unreal
AI agents call get_undo_history 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 |
|---|---|---|---|
count | number | — | Number of recent transactions to return |
Parameters from the server's own tool schema.
Why get_undo_history is rated Low
This tool retrieves and displays historical undo/redo information from Unreal Engine's transaction system. It is purely informational with no side effects—it does not create, modify, delete, or execute any operations. The data returned is read-only metadata about past transactions, making it a Read category tool with low risk.
From the tool's definition Tool name 'get_undo_history' and description 'Get the undo/redo transaction history' indicate a retrieval operation that queries historical transaction data without modifying or executing actions.
Attacks that exploit this kind of access
The rule that runs get_undo_history 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 get_undo_history, this is the rule to start with:
get_undo_history 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 get_undo_history call is checked against it from then on.
Questions about get_undo_history
Get the undo/redo transaction history. It is categorised as a Read tool in the Unreal MCP Server, which means it retrieves data without modifying state.
get_undo_history accepts 1 parameter: count. 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 get_undo_history: 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.
get_undo_history 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_undo_history 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_undo_history. 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_undo_history 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