Create or update a wiki page. For updates, pass expectedVersion for optimistic concurrency. Write-back pattern: read → modify → upsert with expectedVersion.
AI agents use wiki_upsert_page to create or update resources in Shellgate — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Shellgate environment.
This tool creates or modifies wiki pages, which are reversible operations. It does not delete, destroy, or execute arbitrary commands. While it modifies data, the expectedVersion parameter suggests optimistic concurrency control, allowing for potential conflicts but not enabling destructive actions.
From the tool's definition Tool description states: 'Create or update a wiki page.' The operations 'create' and 'update' are explicitly mentioned, and the write-back pattern described (read → modify → upsert) confirms reversible data modification without deletion.
Documented attack patterns abuse exactly the kind of access wiki_upsert_page gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Shellgate, and nothing reaches the server without passing your rules. This is the rule we recommend for wiki_upsert_page:
{
"version": "1",
"default": "deny",
"tools": {
"wiki_upsert_page": {
"limits": [
{
"counter": "wiki_upsert_page_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}wiki_upsert_page stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create or update a wiki page. For updates, pass expectedVersion for optimistic concurrency. Write-back pattern: read → modify → upsert with expectedVersion. It is categorised as a Write tool in the Shellgate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Shellgate MCP server in PolicyLayer and add a rule for wiki_upsert_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 Shellgate. Nothing to install.
wiki_upsert_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 wiki_upsert_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 wiki_upsert_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.
wiki_upsert_page is provided by the Shellgate MCP server (matthiastjong/shellgate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Shellgate, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
31 Shellgate tools catalogued and risk-classified — across an index of 43,000+ MCP servers.