Wiki administration and maintenance. Select
AI agents invoke wiki_admin to trigger actions in Agent Wiki. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Administrative tools typically perform privileged operations that can span multiple categories including configuration changes, user management, or system-level operations. The truncated description ('Select') prevents precise classification. Given it is an admin/maintenance tool on a wiki, it likely can execute privileged operations, potentially including destructive ones.
From the tool's definition 'Wiki administration and maintenance' — description is truncated/uninformative ('Select' appears to be a fragment)
Attacks that exploit this kind of access
Wiki administration and maintenance. Select. It is categorised as a Execute tool in the Agent Wiki MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Agent Wiki MCP server in PolicyLayer and add a rule for wiki_admin: 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 Agent Wiki. Nothing to install.
wiki_admin is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wiki_admin 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_admin. 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_admin is provided by the Agent Wiki MCP server (xinhuagu/agent-wiki). 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 →