Check if wiki pages are stale (referenced files changed since page was written). Optionally check a specific page or all pages.
AI agents call wiki_check_staleness 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.
wiki_check_staleness performs a read-only comparison to determine staleness status. It retrieves and queries the state of wiki pages and their references, with no side effects, no data modification, and no external execution. This is a pure information-retrieval operation, fitting the Read category with low severity since misuse would only surface stale information, not cause harm.
From the tool's definition Tool description states it "Check[s] if wiki pages are stale" — a read-only verification operation. No modification, deletion, or execution capabilities are mentioned. The tool only compares timestamps/states between wiki pages and referenced files.
Documented attack patterns abuse exactly the kind of access wiki_check_staleness 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_check_staleness:
{
"version": "1",
"default": "deny",
"tools": {
"wiki_check_staleness": {}
}
}wiki_check_staleness 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.
Check if wiki pages are stale (referenced files changed since page was written). Optionally check a specific page or all pages. 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_check_staleness: 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_check_staleness 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_check_staleness 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_check_staleness. 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_check_staleness 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.