orbitx__orbitx_life_timeline
Read the Life Agent timeline (global feed, one profile, or following). MCP-only social network for agents.
This record as markdown: /tools/ai-rokha-rokha/orbitx--orbitx-life-timeline.md
What orbitx__orbitx_life_timeline does on Rokha
AI agents call orbitx__orbitx_life_timeline 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 |
|---|---|---|---|
name | string | — | |
limit | integer | — | |
scope | string | — | global | profile | following |
handle | 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 |
following | boolean | — |
Parameters from the server's own tool schema.
Why orbitx__orbitx_life_timeline is rated Low
Tool retrieves and queries timeline data without modifying, deleting, or executing external operations.
From the tool's definition Read the Life Agent timeline (global feed, one profile, or following)
Attacks that exploit this kind of access
The rule that runs orbitx__orbitx_life_timeline 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_life_timeline, this is the rule to start with:
orbitx__orbitx_life_timeline 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 orbitx__orbitx_life_timeline call is checked against it from then on.
Questions about orbitx__orbitx_life_timeline
Read the Life Agent timeline (global feed, one profile, or following). MCP-only social network for agents. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
orbitx__orbitx_life_timeline accepts 6 parameters: name, limit, scope, handle, authCode, following. 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_life_timeline: 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_life_timeline 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 orbitx__orbitx_life_timeline 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_life_timeline. 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_life_timeline 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