List EVERY item currently available in this room's in-game build palette — covers items the user added via P1P (add_to_room_inventory), items the user dragged in via the website's marketplace UI, items from attached inventory lists, and default room-template items. Call this BEFORE arranging a sc...
AI agents call get_room_build_items 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 |
|---|---|---|---|
roomId | string | — | Room id. Falls back to PORTALS_ROOM_ID env. |
Parameters from the server's own tool schema.
This tool queries and retrieves data about available items in a room's build palette. It performs no modifications, deletions, or side effects—it only returns inventory information to inform subsequent operations. This is a standard Read category tool with minimal risk if misused by an AI agent, as the worst outcome would be retrieving information that is already accessible to the user.
From the tool's definition Tool description explicitly states 'List EVERY item currently available' and 'Returns id, name, type, category, glb, thumbnailSrc, audio for each.' The verb 'List' and the read-only nature of querying available items without modification confirms this is a…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List EVERY item currently available in this room's in-game build palette — covers items the user added via P1P (add_to_room_inventory), items the user dragged in via the website's marketplace UI, items from attached inventory lists, and default room-template items. Call this BEFORE arranging a scene with apply_operations so you know which glb URLs and item types are actually available. Returns id, name, type, category, glb, thumbnailSrc, audio for each. It is categorised as a Read tool in the Portals MCP Server, which means it retrieves data without modifying state.
get_room_build_items accepts 1 parameter: roomId. 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_room_build_items: 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_room_build_items 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_room_build_items 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_room_build_items. 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_room_build_items 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.
get_room_build_items is one line of Portals's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →