room_config_get
Requires a JWT. Every setting a Telegram group runs with Rokha: buy bot (token, ticker, room switch, min buy, the platform lane), raids (auto-raids, per hour, length), autopilot (summaries, quiet minutes, drop-ins), shield + X-link guard, room blocklist/trusted counts, X watch, the room's rigs, h...
This record as markdown: /tools/ai-rokha-rokha/room-config-get.md
What room_config_get does on Rokha
AI agents call room_config_get to retrieve information from Rokha without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
chat_id | integer | — | The group's Telegram chat id (negative) |
Parameters from the server's own tool schema.
Why room_config_get is rated Low
Retrieves sensitive Telegram group settings including security configurations and financial parameters with strong access controls.
From the tool's definition JWT required, room settings, founder/admin only, Telegram group configuration, blocklist/trusted counts
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs room_config_get 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_get, this is the rule to start with:
room_config_get is read-only, so it stays allowed. 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_get call is checked against it from then on.
Questions about room_config_get
Requires a JWT. Every setting a Telegram group runs with Rokha: buy bot (token, ticker, room switch, min buy, the platform lane), raids (auto-raids, per hour, length), autopilot (summaries, quiet minutes, drop-ins), shield + X-link guard, room blocklist/trusted counts, X watch, the room's rigs, horde, Seat 0. Only the founder or a monthly subscriber who is an admin of that group (your linked Telegram account). Omit chat_id to list the groups you configured. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
room_config_get accepts 1 parameter: 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_get: 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_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the room_config_get 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_get. 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_get 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