Create or update a wiki page. Content should include YAML frontmatter (title, type, tags, sources) and Markdown body. Timestamps (created/updated) are auto-managed. Auto-routes root-level pages to matching topic subdirectories (via frontmatter
AI agents use wiki_write to create or update resources in Agent Wiki — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Wiki environment.
This tool creates or modifies wiki pages with structured content (YAML frontmatter + Markdown). While it persists data, the operations are inherently reversible—pages can be edited, deleted, or reverted. The sibling tool 'wiki_delete' exists separately, indicating deletion is a distinct operation.
From the tool's definition Tool description explicitly states 'Create or update a wiki page' and 'auto-manages timestamps' and 'auto-routes' content. These are reversible modifications to structured knowledge data.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Create or update a wiki page. Content should include YAML frontmatter (title, type, tags, sources) and Markdown body. Timestamps (created/updated) are auto-managed. Auto-routes root-level pages to matching topic subdirectories (via frontmatter. It is categorised as a Write tool in the Agent Wiki MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent Wiki 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 Agent Wiki. 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 Agent Wiki MCP server (xinhuagu/agent-wiki). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
wiki_write is one line of Agent Wiki's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →