get_input_mapping_context
Read all key mappings from an Input Mapping Context.
This record as markdown: /tools/aadeshrao123-unreal-mcp/get-input-mapping-context.md
What get_input_mapping_context does on Unreal-MCP
AI agents call get_input_mapping_context to retrieve information from Unreal-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_input_mapping_context is rated Low
This tool retrieves existing input mapping configuration data from Unreal Engine without creating, modifying, or deleting any assets. It has no side effects and poses minimal security risk—an AI agent misusing it could only view key bindings, not alter game controls or cause harm.
From the tool's definition Tool name includes 'get_' prefix and description states 'Read all key mappings' — explicitly a read operation with no modification capability.
Attacks that exploit this kind of access
The rule that runs get_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 get_input_mapping_context, this is the rule to start with:
get_input_mapping_context 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 Unreal-MCP, apply this rule, and every get_input_mapping_context call is checked against it from then on.
Questions about get_input_mapping_context
Read all key mappings from an Input Mapping Context. It is categorised as a Read tool in the Unreal-MCP MCP Server, which means it retrieves data without modifying state.
Register the Unreal MCP server in PolicyLayer and add a rule for get_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.
get_input_mapping_context 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_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 get_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.
get_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