AI agents call wiki_info to retrieve information from Wikimcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves informational data (stats and schema instructions) about the wiki. It has no side effects and is purely a read operation. Low severity since it only exposes metadata.
From the tool's definition Return wiki stats and schema instructions
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Return wiki stats and schema instructions. MUST be called at the start of every session. It is categorised as a Read tool in the Wikimcp MCP Server, which means it retrieves data without modifying state.
Register the Wiki MCP server in PolicyLayer and add a rule for wiki_info: 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 Wikimcp. Nothing to install.
wiki_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the wiki_info 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_info. 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_info is provided by the Wiki MCP server (mohith-das/wikimcp). 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 →