room_config_set
Requires a JWT. Same authority as room_config_get. sets = up to 8 {key: value}: autopilot, auto_raids, chatter (on/off); raid_minutes, raids_per_hour, quiet_minutes, summaries_per_hour, dropins_per_hour (numbers, clamped to the /manage bands); buybot (on/off), buybot_token (a Solana mint), buybot...
This record as markdown: /tools/ai-rokha-rokha/room-config-set.md
What room_config_set does on Rokha
AI agents use room_config_set to create or update resources in Rokha, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rokha environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
sets | object | Yes | |
chat_id | integer | Yes |
Parameters from the server's own tool schema.
Why room_config_set is rated Medium
Modifies room settings including financial trading parameters (buybot_token, buybot_min) and automation controls.
From the tool's definition sets room configuration: autopilot, auto_raids, buybot, shield, buybot_token, buybot_min USD.
Attacks that exploit this kind of access
The rule that runs room_config_set safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For room_config_set, this is the rule to start with:
room_config_set stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every room_config_set call is checked against it from then on.
Questions about room_config_set
Requires a JWT. Same authority as room_config_get. sets = up to 8 {key: value}: autopilot, auto_raids, chatter (on/off); raid_minutes, raids_per_hour, quiet_minutes, summaries_per_hour, dropins_per_hour (numbers, clamped to the /manage bands); buybot (on/off), buybot_token (a Solana mint), buybot_symbol (ticker), buybot_min (USD, 1-100000), buybot_spotlights (on/off); shield, x_link_guard (on/off). Returns each result and the room's settings after. It is categorised as a Write tool in the Rokha MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
room_config_set accepts 2 parameters: sets, chat_id. Required: sets, chat_id. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for room_config_set: 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 Rokha. Nothing to install.
room_config_set 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 room_config_set 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 room_config_set. 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.
room_config_set is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rokha, and thousands of servers like it.
This server
Across the catalogue