Low Risk

wiki_read

Read a wiki page by name, or list all wiki pages if no name is given.

How to control wiki_read ↓

AI agents call wiki_read to retrieve information from Reporecall without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves wiki page content or lists available pages. These are pure read operations that do not create, modify, delete, or execute anything. The blast radius of misuse is minimal — exposure of documentation or information already intended to be readable.

From the tool's definition Tool name 'wiki_read' and description 'Read a wiki page by name, or list all wiki pages if no name is given' — both indicate data retrieval operations with no modification or side effects.

Documented attack patterns abuse exactly the kind of access wiki_read gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Reporecall, and nothing reaches the server without passing your rules. This is the rule we recommend for wiki_read:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "wiki_read": {}
  }
}

wiki_read is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Reporecall — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the wiki_read tool do? +

Read a wiki page by name, or list all wiki pages if no name is given. It is categorised as a Read tool in the Reporecall MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on wiki_read? +

Register the Reporecall MCP server in PolicyLayer and add a rule for wiki_read: 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 Reporecall. Nothing to install.

What risk level is wiki_read? +

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

Can I rate-limit wiki_read? +

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

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

wiki_read is provided by the Reporecall MCP server (proofofwork-agency/reporecall). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Reporecall tool call.

Deterministic rules across all 30 Reporecall tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

30 Reporecall tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.