remove_mapping_modifier
Remove a modifier from a mapping in an Input Mapping Context.
This record as markdown: /tools/aadeshrao123-unreal-mcp/remove-mapping-modifier.md
What remove_mapping_modifier does on Unreal-MCP
AI agents call remove_mapping_modifier 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_mapping_modifier is rated Critical
Removing a modifier from a mapping is a destructive operation that deletes configuration data from the Input Mapping Context. While the Unreal Editor may have undo history, MCP-driven operations are often not easily reversible and the modifier configuration is deleted rather than just modified. Severity is medium as it affects editor asset configuration but not runtime data or financial systems.
From the tool's definition 'Remove a modifier from a mapping' — irreversibly removes a modifier configuration from an Input Mapping Context
Attacks that exploit this kind of access
The rule that runs remove_mapping_modifier 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_mapping_modifier, this is the rule to start with:
remove_mapping_modifier 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_mapping_modifier call is checked against it from then on.
Questions about remove_mapping_modifier
Remove a modifier from a mapping in an Input Mapping Context. 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_mapping_modifier: 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_mapping_modifier 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_mapping_modifier 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_mapping_modifier. 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_mapping_modifier 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