AI agents use update_index to create or update resources in Wikimcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wikimcp environment.
This tool modifies the wiki's index file (a reversible write operation). Although it overwrites existing content, the git-backed nature of the system means the previous version remains recoverable via version control, preventing it from being classified as Destructive. The impact is scoped to the index file rather than arbitrary code execution.
From the tool's definition Tool description states "Overwrite index.md with new content and auto-commit." The verb "overwrite" indicates modification of existing data, while "auto-commit" shows the change is persisted to git.
Attacks that exploit this kind of access
Overwrite index.md with new content and auto-commit. It is categorised as a Write tool in the Wikimcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wiki MCP server in PolicyLayer and add a rule for update_index: 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 Wikimcp. Nothing to install.
update_index 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 update_index 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 update_index. 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.
update_index is provided by the Wiki MCP server (mohith-das/wikimcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
update_index is one line of 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 →