create_input_mapping_context
Create a new UInputMappingContext asset.
This record as markdown: /tools/aadeshrao123-unreal-mcp/create-input-mapping-context.md
What create_input_mapping_context does on Unreal-MCP
AI agents use create_input_mapping_context to create or update resources in Unreal-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unreal-MCP environment.
Why create_input_mapping_context is rated Medium
This tool creates new data (an input mapping context asset) in the Unreal Engine editor, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. The severity is medium because misuse could create unwanted input mappings that affect game controls, but the effect is limited in scope and can be undone by deleting the asset.
From the tool's definition Tool name 'create_input_mapping_context' and description 'Create a new UInputMappingContext asset' explicitly perform a creation operation that modifies the Unreal Engine project by adding a new asset.
Attacks that exploit this kind of access
The rule that runs create_input_mapping_context 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 create_input_mapping_context, this is the rule to start with:
create_input_mapping_context stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Unreal-MCP, apply this rule, and every create_input_mapping_context call is checked against it from then on.
Questions about create_input_mapping_context
Create a new UInputMappingContext asset. It is categorised as a Write tool in the Unreal-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unreal MCP server in PolicyLayer and add a rule for create_input_mapping_context: 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.
create_input_mapping_context is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_input_mapping_context 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 create_input_mapping_context. 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.
create_input_mapping_context 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.
This server
Across the catalogue