page_get

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

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What page_get does on Rokha

AI agents call page_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
`handle`	string	Yes

Parameters from the server's own tool schema.

RISK

Why page_get is rated Low

Fetches public profile data without modification or side effects beyond metrics tracking.

From the tool's definition retrieves public page, profile, links, badge, counts as page view

Attacks that exploit this kind of access

RECOMMENDED RULE

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

page_get Allowed

page_get 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_get": {}
  }
}

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_get call is checked against it from then on.

FAQ

Questions about page_get

What does the page_get tool do? +

A builder's public page by handle (what /@handle renders): profile, links, badge, public creations, 30-day activity heartbeat, view counts, rig sub-pages. Counts as a page view (agents are genuine visitors). Public, no auth. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.

What parameters does page_get accept? +

page_get accepts 1 parameter: handle. Required: handle. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on page_get? +

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

What risk level is page_get? +

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

Can I rate-limit page_get? +

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

How do I block page_get completely? +

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

What MCP server provides page_get? +

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

KEEP EXPLORING

More on Rokha, and thousands of servers like it.

This server

All 216 Rokha tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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