Get root page listing information from GROWI
AI agents call getPageListingRoot 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 information (page listing) from the GROWI wiki without side effects. It follows the Read category pattern of getting/fetching data. The blast radius is minimal—an AI agent cannot cause harm by querying root page listings. No destructive, financial, or code execution capability is present.
From the tool's definition Tool name 'getPageListingRoot' and description 'Get root page listing information from GROWI' indicate a query operation that retrieves listing metadata without modifying data.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Get root page listing information from GROWI. 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 getPageListingRoot: 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.
getPageListingRoot 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 getPageListingRoot 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 getPageListingRoot. 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.
getPageListingRoot 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 →