list_page_tags
AI agents call list_page_tags 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.
The tool appears to query and return page tags, which is a read-only operation with no side effects. No data is created, modified, or deleted. The empty description lowers confidence slightly, but the naming convention and server context strongly suggest a retrieval function. Severity is low because tag enumeration poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'list_page_tags' indicates a listing/retrieval operation. Description is empty, but sibling tools like 'get_page_by_path', 'get_page_history', and 'explore_knowledge_graph' establish this server's Read category pattern.
Attacks that exploit this kind of access
list_page_tags. 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 list_page_tags: 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.
list_page_tags 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 list_page_tags 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 list_page_tags. 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.
list_page_tags 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 →