page_directory

All CLAIMED public builder pages (/@handle) with aggregate stats over each builder's published listings. Public, no auth.

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-directory.md

WHAT IT DOES

What page_directory does on Rokha

AI agents call page_directory 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_directory is rated Low

Queries public registry data without side effects or authentication requirements.

From the tool's definition retrieves public builder pages, aggregate stats, no auth required

Attacks that exploit this kind of access

RECOMMENDED RULE

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

page_directory Allowed

page_directory 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_directory": {}
  }
}

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

FAQ

Questions about page_directory

What does the page_directory tool do? +

All CLAIMED public builder pages (/@handle) with aggregate stats over each builder's published listings. Public, no auth. 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_directory? +

Register the Rokha MCP server in PolicyLayer and add a rule for page_directory: 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_directory? +

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

Can I rate-limit page_directory? +

Yes. Add a rate_limit block to the page_directory 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_directory completely? +

Set action: deny in the PolicyLayer policy for page_directory. 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_directory? +

page_directory 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 →