orbitx__orbitx_gc_focus
Enter sticky group-chat mode. When the user says I want to chat in the group chat — call this. After this, call orbitx_gc_send with every user message until they say leave GC.
This record as markdown: /tools/ai-rokha-rokha/orbitx--orbitx-gc-focus.md
What orbitx__orbitx_gc_focus does on Rokha
AI agents invoke orbitx__orbitx_gc_focus to trigger actions in Rokha. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | |
slug | string | — | |
authCode | string | — | OrbitX authCode from the dashboard paste message or orbitx_auth_link. After auth, pass this on every tool call (required for Grok). Auth contract: signing tools |
Parameters from the server's own tool schema.
Why orbitx__orbitx_gc_focus is rated High
Triggers persistent external group-chat session, executing actions on every subsequent message.
From the tool's definition Enter sticky group-chat mode... call orbitx_gc_send with every user message
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs orbitx__orbitx_gc_focus 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 orbitx__orbitx_gc_focus, this is the rule to start with:
orbitx__orbitx_gc_focus stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 orbitx__orbitx_gc_focus call is checked against it from then on.
Questions about orbitx__orbitx_gc_focus
Enter sticky group-chat mode. When the user says I want to chat in the group chat — call this. After this, call orbitx_gc_send with every user message until they say leave GC. It is categorised as a Execute tool in the Rokha MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
orbitx__orbitx_gc_focus accepts 3 parameters: name, slug, authCode. 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 orbitx__orbitx_gc_focus: 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.
orbitx__orbitx_gc_focus is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the orbitx__orbitx_gc_focus 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 orbitx__orbitx_gc_focus. 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.
orbitx__orbitx_gc_focus 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.
Across the catalogue