Get summary information for pages in GROWI by IDs or path
AI agents call pageListingInfo to retrieve information from GROWI 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 page metadata and summary information without creating, modifying, deleting, or executing any operations. It is a pure query/fetch operation that has no adverse effects if called by an AI agent, even with arbitrary page IDs or paths. Low severity because the worst case is unauthorized information disclosure of wiki page metadata.
From the tool's definition Tool description states 'Get summary information for pages in GROWI by IDs or path' — a retrieval operation with no modification or side effects. The name 'pageListingInfo' and verb 'Get' indicate read-only data access.
Attacks that exploit this kind of access
Get summary information for pages in GROWI by IDs or path. It is categorised as a Read tool in the GROWI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GROWI MCP Server MCP server in PolicyLayer and add a rule for pageListingInfo: 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 GROWI MCP Server. Nothing to install.
pageListingInfo 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 pageListingInfo 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 pageListingInfo. 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.
pageListingInfo is provided by the GROWI MCP Server MCP server (mechanicalgirldev/growi-mcp-server-web). 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 →