remove_key_mapping
A destructive tool on the Unreal- MCP server.
This record as markdown: /tools/aadeshrao123-unreal-mcp/remove-key-mapping.md
What remove_key_mapping does on Unreal-MCP
AI agents call remove_key_mapping to permanently remove resources in Unreal-MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_key_mapping is rated Critical
The tool removes key mappings, which are configuration data in Unreal Engine. Removal of mappings is irreversible and cannot be easily undone within the tool's scope—an AI agent misusing this could delete critical input bindings needed for game functionality.
From the tool's definition Tool name 'remove_key_mapping' indicates deletion/removal of input key mappings. Sibling tools like 'add_key_mapping' suggest this modifies Unreal Engine input configuration. The 'remove' verb indicates irreversible deletion of configuration data.
Attacks that exploit this kind of access
The rule that runs remove_key_mapping safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_key_mapping, this is the rule to start with:
remove_key_mapping is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Unreal-MCP, apply this rule, and every remove_key_mapping call is checked against it from then on.
Questions about remove_key_mapping
remove_key_mapping is a destructive tool on the Unreal MCP server. It is categorised as a Destructive tool in the Unreal-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Unreal MCP server in PolicyLayer and add a rule for remove_key_mapping: 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-MCP. Nothing to install.
remove_key_mapping is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_key_mapping 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 remove_key_mapping. 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.
remove_key_mapping is provided by the Unreal MCP server (aadeshrao123/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.
Across the catalogue