Search wiki pages by keyword. Returns matching wiki pages with summaries. Use this to find existing codebase knowledge before exploring from scratch.
AI agents call wiki_query 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.
This tool performs a read-only search operation that retrieves information from wiki pages. It has no side effects—no data is created, modified, deleted, or executed. The blast radius of misuse is minimal; an agent could only retrieve irrelevant documentation. This is a classic Read category tool.
From the tool's definition Tool name 'wiki_query' and description 'Search wiki pages by keyword. Returns matching wiki pages with summaries' indicate a retrieval-only operation. The action is to query and return data without modifying state.
Documented attack patterns abuse exactly the kind of access wiki_query 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_query:
{
"version": "1",
"default": "deny",
"tools": {
"wiki_query": {}
}
}wiki_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search wiki pages by keyword. Returns matching wiki pages with summaries. Use this to find existing codebase knowledge before exploring from scratch. It is categorised as a Read tool in the Reporecall MCP Server, which means it retrieves data without modifying state.
Register the Reporecall MCP server in PolicyLayer and add a rule for wiki_query: 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.
wiki_query 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 wiki_query 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 wiki_query. 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.
wiki_query 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.
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.