List revisions for a page in GROWI with pagination support
AI agents call listRevisions 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 performs a read-only operation that queries and lists existing page revision history. It has no side effects, does not modify data, and does not execute code or trigger external operations. The pagination support further confirms it is a data retrieval utility. No destructive, write, execute, or financial operations are involved.
From the tool's definition Tool name 'listRevisions' and description 'List revisions for a page in GROWI with pagination support' indicate a retrieval/query operation that retrieves historical revision data without modifying or deleting content.
Attacks that exploit this kind of access
List revisions for a page in GROWI with pagination support. 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 listRevisions: 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.
listRevisions 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 listRevisions 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 listRevisions. 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.
listRevisions 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 →