Create or update a wiki page manually. Use this to persist codebase knowledge that should be available in future sessions.
AI agents use wiki_write to create or update resources in Reporecall — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Reporecall environment.
This tool creates or modifies wiki pages, which is a reversible write operation. It does not delete data (would be Destructive), does not move financial resources (would be Financial), and does not execute arbitrary code (would be Execute).
From the tool's definition Create or update a wiki page manually. Use this to persist codebase knowledge that should be available in future sessions. The verbs 'create' and 'update' indicate reversible modification of data (wiki pages).
Documented attack patterns abuse exactly the kind of access wiki_write 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_write:
{
"version": "1",
"default": "deny",
"tools": {
"wiki_write": {
"limits": [
{
"counter": "wiki_write_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}wiki_write stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create or update a wiki page manually. Use this to persist codebase knowledge that should be available in future sessions. It is categorised as a Write tool in the Reporecall MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Reporecall MCP server in PolicyLayer and add a rule for wiki_write: 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_write is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the wiki_write 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_write. 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_write 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.