AI agents use update_room_settings to create or update resources in Portals — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Portals environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
Name | string | — | Room name |
Image | string | — | Room cover image URL |
roomId | string | — | Room ID to update. Falls back to PORTALS_ROOM_ID env variable if omitted. |
Discord | string | — | Room Discord invite URL |
HighRes | boolean | — | Enable high resolution mode |
Purpose | string | — | Room purpose/category |
MuteGuests | boolean | — | Mute guests by default |
Description | string | — | Room description |
CustomLoader | boolean | — | Enable custom loading screen behavior |
LoadingImages | array | — | Array of loading screen image URLs. CustomLoader will be set to true automatically. |
ShowOnDirectory | boolean | — | Show room in the public directory |
PasswordProtected | boolean | — | Enable password protection |
Parameters from the server's own tool schema.
This tool creates or modifies room configuration data (name, description, image, visibility settings). The modifications are reversible—settings can be changed again. It does not execute code, delete data, move money, or trigger external operations.
From the tool's definition Tool name 'update_room_settings' and description 'Update room settings like name, description, image, visibility, etc.' indicate modification of existing data structures without deletion or external execution.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
Update room settings like name, description, image, visibility, etc. It is categorised as a Write tool in the Portals MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_room_settings accepts 12 parameters: Name, Image, roomId, Discord, HighRes, Purpose, MuteGuests, Description, CustomLoader, LoadingImages, ShowOnDirectory, PasswordProtected. 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 update_room_settings: 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.
update_room_settings is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_room_settings 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 update_room_settings. 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.
update_room_settings 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 →