Audit Portals Trigger-zone pressBtn/keyCode behavior and optionally simulate enter/exit/key frames. Use this for the Trigger cube setting labeled Press Key To Activate: pressBtn gates OnEnterEvent tasks until the player is inside the zone and presses keyCode. This is separate from global OnKeyPre...
AI agents invoke simulate_trigger_zone_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 to simulate. Example: [{type:'enter', itemId:'12'}, {type:'press', key:'X'}]. Omit for a static Trigger-zone audit. |
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 code/operations by simulating input events that cause external state changes in the Portals application (triggering task execution, zone activation). While the effects are within the application's sandbox and appear reversible, the tool's purpose is to trigger behaviors and state transitions based on simulated user actions, fitting the Execute category.
From the tool's definition The tool 'simulate_trigger_zone_input' directly simulates user input actions (enter/exit/key frames) and triggers events within a game/application environment.
Risk signalsAccepts file system path (filePath)
Attacks that exploit this kind of access
Audit Portals Trigger-zone pressBtn/keyCode behavior and optionally simulate enter/exit/key frames. Use this for the Trigger cube setting labeled Press Key To Activate: pressBtn gates OnEnterEvent tasks until the player is inside the zone and presses keyCode. This is separate from global OnKeyPressedEvent subscriptions. 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_trigger_zone_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_trigger_zone_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_trigger_zone_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_trigger_zone_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_trigger_zone_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_trigger_zone_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 →