update_wiki
AI agents use update_wiki to create or update resources in TAPD MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TAPD MCP Server environment.
The tool modifies wiki content, which is reversible (can be edited again or reverted), placing it in the Write category rather than Read or Destructive. Severity is medium because unauthorized wiki modifications could impact team knowledge/documentation but typically lack the irreversibility of Destructive actions or financial impact.
From the tool's definition Tool name 'update_wiki' indicates modification of wiki documentation/content. No description provided, but context shows this is part of TAPD project management platform where wiki updates would modify project documentation.
Attacks that exploit this kind of access
update_wiki. It is categorised as a Write tool in the TAPD MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TAPD MCP Server MCP server in PolicyLayer and add a rule for update_wiki: 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 TAPD MCP Server. Nothing to install.
update_wiki 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_wiki 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_wiki. 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_wiki is provided by the TAPD MCP Server MCP server (ken19990709/mcp-server-for-tapd). 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 →