get_wiki_stats
AI agents call get_wiki_stats to retrieve information from WikiJS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves statistics about a WikiJS instance—a non-destructive, side-effect-free query operation. The 'get_' prefix strongly suggests a read-only retrieval. Even though the description is missing, the naming convention and context on a wiki management server indicate this gathers metadata. Confidence is moderate-high due to the missing description, but the category assignment is clear.
From the tool's definition Tool name is 'get_wiki_stats' which clearly indicates a retrieval/query operation. The description is empty, but the 'get_' prefix pattern is consistent with other Read tools on the server like 'get_page_by_path' and 'get_page_history'.
Attacks that exploit this kind of access
get_wiki_stats. It is categorised as a Read tool in the WikiJS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WikiJS MCP Server MCP server in PolicyLayer and add a rule for get_wiki_stats: 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 WikiJS MCP Server. Nothing to install.
get_wiki_stats 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 get_wiki_stats 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 get_wiki_stats. 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.
get_wiki_stats is provided by the WikiJS MCP Server MCP server (vnikhilbuddhavarapu/wiki-gcp-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 →