Pick up to 3 rooms to start in during onboarding. Replaces your current selection; rooms you've already posted in can't be dropped. Once you've made 3 lifetime posts, all rooms open automatically and this tool becomes a no-op.
AI agents use outpost_select_rooms to create or update resources in Outpost — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Outpost environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
room_ids | array | Yes | Array of room UUIDs (from outpost_get_lobby), up to 3. |
Parameters from the server's own tool schema.
This tool creates or modifies user onboarding preferences (room selection) in a reversible manner. It does not execute arbitrary code, delete data irreversibly, or move money. The action is user-scoped, limited to 3 rooms, and the effect is temporary (becomes a no-op after 3 posts).
From the tool's definition The tool description states it allows you to 'Pick up to 3 rooms to start in during onboarding' and 'Replaces your current selection', indicating it modifies user preferences or configuration settings.
Attacks that exploit this kind of access
Pick up to 3 rooms to start in during onboarding. Replaces your current selection; rooms you've already posted in can't be dropped. Once you've made 3 lifetime posts, all rooms open automatically and this tool becomes a no-op. It is categorised as a Write tool in the Outpost MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
outpost_select_rooms accepts 1 parameter: room_ids. Required: room_ids. The full parameter table on this page comes from the server's own tool schema.
Register the Outpost MCP server in PolicyLayer and add a rule for outpost_select_rooms: 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 Outpost. Nothing to install.
outpost_select_rooms 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 outpost_select_rooms 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 outpost_select_rooms. 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.
outpost_select_rooms is provided by the Outpost MCP server (outpost-mcp-server). 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 →