remove_mapping_trigger

Remove a trigger from a mapping in an Input Mapping Context.

SERVERUnreal-MCP SOURCEaadeshrao123/unreal-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aadeshrao123-unreal-mcp/remove-mapping-trigger.md

WHAT IT DOES

What remove_mapping_trigger does on Unreal-MCP

AI agents call remove_mapping_trigger 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.

RISK

Why remove_mapping_trigger is rated Critical

Removing a trigger from an input mapping context is an irreversible deletion of configuration data. While it can potentially be re-added, the action itself destroys existing mapping configuration without a built-in undo mechanism at the tool level, fitting the Destructive category.

From the tool's definition 'Remove a trigger from a mapping' — permanently removes configuration data from an Input Mapping Context

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_mapping_trigger 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_trigger, this is the rule to start with:

remove_mapping_trigger Hidden

remove_mapping_trigger is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_mapping_trigger"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Unreal-MCP, apply this rule, and every remove_mapping_trigger call is checked against it from then on.

FAQ

Questions about remove_mapping_trigger

What does the remove_mapping_trigger tool do? +

Remove a trigger 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.

How do I enforce a policy on remove_mapping_trigger? +

Register the Unreal MCP server in PolicyLayer and add a rule for remove_mapping_trigger: 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.

What risk level is remove_mapping_trigger? +

remove_mapping_trigger is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_mapping_trigger? +

Yes. Add a rate_limit block to the remove_mapping_trigger 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.

How do I block remove_mapping_trigger completely? +

Set action: deny in the PolicyLayer policy for remove_mapping_trigger. 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.

What MCP server provides remove_mapping_trigger? +

remove_mapping_trigger 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.

KEEP EXPLORING

More on Unreal, and thousands of servers like it.

This server

All 286 Unreal tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →