get_undo_history
Lista o historico de acoes que podem ser desfeitas.
This record as markdown: /tools/mcp-godot-desenvolvimento/get-undo-history.md
What get_undo_history does on Mcp Godot Desenvolvimento
AI agents call get_undo_history to retrieve information from Mcp Godot Desenvolvimento without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_undo_history is rated Low
Even though get_undo_history only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
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 Mcp Godot Desenvolvimento, 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 Mcp Godot Desenvolvimento, apply this rule, and every get_undo_history call is checked against it from then on.
Questions about get_undo_history
Lista o historico de acoes que podem ser desfeitas. It is categorised as a Read tool in the Mcp Godot Desenvolvimento MCP Server, which means it retrieves data without modifying state.
Register the Mcp Godot Desenvolvimento 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 Mcp Godot Desenvolvimento. 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 Mcp Godot Desenvolvimento MCP server (joabcostamd/mcp-godot-desenvolvimento). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Godot Desenvolvimento, and thousands of servers like it.
This server
Across the catalogue