AI agents use create_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 |
|---|---|---|---|
templateName | string | Yes | Template to create the room from |
customTemplateName | string | — | Name for the room |
Parameters from the server's own tool schema.
This tool creates new data (a room resource) that is stored persistently and can be modified or deleted later. It is reversible (the room can be deleted), so it does not qualify as Destructive. It has no financial impact, does not execute arbitrary code, and actively modifies state rather than merely reading. Write is the appropriate category.
From the tool's definition Tool description states 'Create a new room from a template' — the verb 'create' and the action of generating a new persistent entity (room ID) indicates data creation.
Attacks that exploit this kind of access
Create a new room from a template. 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.
create_room accepts 2 parameters: templateName, customTemplateName. Required: templateName. 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 create_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.
create_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 create_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 create_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.
create_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 →