AI agents use duplicate_room 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 |
|---|---|---|---|
roomId | string | — | Room ID to duplicate. Falls back to PORTALS_ROOM_ID env variable if omitted. |
Parameters from the server's own tool schema.
This tool creates a new room by copying an existing one, which is a reversible write/create operation. It does not delete or overwrite data, execute arbitrary code, or involve financial transactions. The blast radius is medium since it could create large duplicate resources, but it is not irreversible.
From the tool's definition Duplicate an existing room. Creates a copy with all items, settings, tasks, and quests. Returns the new room ID.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Duplicate an existing room. Creates a copy with all items, settings, tasks, and quests. Returns the new room ID. 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.
duplicate_room 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 duplicate_room: 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.
duplicate_room 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 duplicate_room 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 duplicate_room. 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.
duplicate_room 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 →