Update a Wiki page in Backlog
AI agents use update_wiki_page to create or update resources in Backlog MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Backlog MCP Server environment.
The tool modifies wiki page data in the Backlog system, which is a classic Write operation—data is created or altered but can be undone (previous versions typically exist in wiki systems). Severity is medium because wiki page modifications could impact team documentation and knowledge sharing, but the operation is reversible and lacks the irreversibility of Destructive operations or financial consequences.
From the tool's definition Tool name 'update_wiki_page' and description 'Update a Wiki page in Backlog' directly indicate modification of existing wiki page content. This is a reversible write operation.
Attacks that exploit this kind of access
Update a Wiki page in Backlog. It is categorised as a Write tool in the Backlog MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Backlog MCP Server MCP server in PolicyLayer and add a rule for update_wiki_page: 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 Backlog MCP Server. Nothing to install.
update_wiki_page 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_page 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_page. 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_page is provided by the Backlog MCP Server MCP server (katsuhirohonda/mcp-backlog-server). 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 →