AI agents use create_or_update_wiki_page to create or update resources in Redmine — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Redmine environment.
This tool modifies wiki content reversibly. It does not delete data (which would be Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). While wiki pages can be important documentation, the modification is reversible—pages can be edited again or reverted.
From the tool's definition Tool description explicitly states "Create or replace a wiki page". The PUT operation is described as an upsert, meaning it creates new wiki pages or modifies existing ones. Both creation and modification of content are reversible write operations.
Attacks that exploit this kind of access
Create or replace a wiki page (Redmine PUT is upsert). It is categorised as a Write tool in the Redmine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Redmine MCP server in PolicyLayer and add a rule for create_or_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 Redmine. Nothing to install.
create_or_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 create_or_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 create_or_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.
create_or_update_wiki_page is provided by the Redmine MCP server (KalvadTech/redmine-mcp). 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 →