Audit Portals OnKeyPressedEvent/OnKeyReleasedEvent trigger mappings and optionally simulate key press/release frames. Uses the same key-code names and matching semantics as Unity InputHandler. Use this before live testing keyboard-triggered logic to verify that the configured key fields would sub...
AI agents invoke simulate_key_input to trigger actions in Portals. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
roomId | string | — | Room ID to download and audit. Falls back to PORTALS_ROOM_ID if omitted and filePath is not provided. |
actions | array | — | Optional sequence of key frames to simulate. Omit to return a static subscription audit only. |
filePath | string | — | Absolute path to a snapshot.json file. Prefer the file_path from get_room_data for local audits. |
Parameters from the server's own tool schema.
This tool executes keyboard input simulation that directly triggers event handlers and game logic flows. While presented as an audit/verification tool, the ability to simulate key press/release frames constitutes execution of external operations.
From the tool's definition simulate_key_input simulates key press/release frames and triggers OnKeyPressedEvent/OnKeyReleasedEvent mappings, which are external operations whose effects depend on how keyboard-triggered logic is configured in the application.
Risk signalsAccepts file system path (filePath)
Attacks that exploit this kind of access
Audit Portals OnKeyPressedEvent/OnKeyReleasedEvent trigger mappings and optionally simulate key press/release frames. Uses the same key-code names and matching semantics as Unity InputHandler. Use this before live testing keyboard-triggered logic to verify that the configured key fields would subscribe and fire. It is categorised as a Execute tool in the Portals MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
simulate_key_input accepts 3 parameters: roomId, actions, filePath. The full parameter table on this page comes from the server's own tool schema.
Register the Portals MCP server in PolicyLayer and add a rule for simulate_key_input: 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 Portals. Nothing to install.
simulate_key_input is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the simulate_key_input 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 simulate_key_input. 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.
simulate_key_input is provided by the Portals MCP server (portals-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →