Rename / retitle a tag.
AI agents use wiki_tag_update to create or update resources in Mcp Wikijs Mv — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Wikijs Mv environment.
This tool updates tag properties (name/title) rather than deleting or creating tags. It is reversible—the previous tag name can be restored by calling the tool again. The blast radius is medium: renaming tags could break tag-based navigation or searches if done maliciously across many tags, but the change can be undone. This is a clear Write operation with no destructive, financial, or execute characteristics.
From the tool's definition Tool description states 'Rename / retitle a tag', which modifies existing tag metadata. Related tools on the server include wiki_tag_delete (destructive) and wiki_tag_create (write), confirming this is a modification operation.
Attacks that exploit this kind of access
Rename / retitle a tag. It is categorised as a Write tool in the Mcp Wikijs Mv MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Wikijs Mv MCP server in PolicyLayer and add a rule for wiki_tag_update: 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 Mcp Wikijs Mv. Nothing to install.
wiki_tag_update 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_tag_update 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_tag_update. 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_tag_update is provided by the Mcp Wikijs Mv MCP server (janschachtschabel/mcp-for-wiki-js). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →