Fetch live runtime variables and JS function effector results from the Unity game client. Returns numeric parameters, string parameters, and player variables currently active in the scene. Also drains any queued JS effector results that have fired since the last call. IMPORTANT: Use this tool to ...
AI agents call get_runtime_data to retrieve information from Portals without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
includeEffectorResults | boolean | — | Whether to include queued JS effector results in the response. Default true. |
Parameters from the server's own tool schema.
The tool queries and retrieves the current state of runtime variables, parameters, and effector results from the Unity game client. It performs no modifications, deletions, or side effects beyond consuming queued results (a normal read operation). This is purely informational and used for testing/debugging, making it a Read category tool with low risk.
From the tool's definition Fetch live runtime variables", "Returns numeric parameters, string parameters, and player variables", "drains any queued JS effector results" — all retrieval operations with no modifications.
Attacks that exploit this kind of access
Fetch live runtime variables and JS function effector results from the Unity game client. Returns numeric parameters, string parameters, and player variables currently active in the scene. Also drains any queued JS effector results that have fired since the last call. IMPORTANT: Use this tool to test and debug your implementations. After applying operations that set variables, create logic, or add JS effectors, call this tool to verify the runtime state matches your expectations. This is the primary way to confirm your changes are working correctly in the live game. It is categorised as a Read tool in the Portals MCP Server, which means it retrieves data without modifying state.
get_runtime_data accepts 1 parameter: includeEffectorResults. 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 get_runtime_data: 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.
get_runtime_data 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_runtime_data 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_runtime_data. 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_runtime_data 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 →