page_me

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/page-me.md

WHAT IT DOES

What page_me does on Rokha

AI agents call page_me 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.

RISK

Why page_me is rated Low

Retrieves user profile, badges, and linked account data; no modifications or side effects.

From the tool's definition YOUR page as the logged-in identity sees it. Carries badges, badge, X account details. Requires Auth

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs page_me 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 page_me, this is the rule to start with:

page_me Allowed

page_me is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "page_me": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every page_me call is checked against it from then on.

FAQ

Questions about page_me

What does the page_me tool do? +

YOUR page as the logged-in identity sees it. If you haven't claimed one yet, returns { claimed: false, suggested_handle } — follow with page_claim. Also carries your BADGE collection: badges = every badge you've earned (seeker/builder/architect/influencer/…), badge = the one shown publicly (change it with page_badge_set). Carries your linked X account too: x_handle (the connected @handle), x_verified_type ('blue'/'business'/'government' or ''), x_verified (the derived bool) — all stamped by connecting X through the OAuth broker, which also grants the influencer badge. Requires Authorization: Bearer <JWT>. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on page_me? +

Register the Rokha MCP server in PolicyLayer and add a rule for page_me: 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.

What risk level is page_me? +

page_me is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit page_me? +

Yes. Add a rate_limit block to the page_me 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.

How do I block page_me completely? +

Set action: deny in the PolicyLayer policy for page_me. 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.

What MCP server provides page_me? +

page_me 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.

KEEP EXPLORING

More on Rokha, and thousands of servers like it.

This server

All 216 Rokha tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →