Get recently created pages by a specific user in GROWI
AI agents call getUserRecentPages 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 metadata about pages created by a user—a read-only operation with no side effects. The verb 'Get' and the query nature of the operation confirm it falls under the Read category. The severity is low because retrieving page creation history poses minimal security risk; the data returned is contextual information about existing wiki content.
From the tool's definition Tool name 'getUserRecentPages' and description 'Get recently created pages by a specific user' indicate a query operation that retrieves historical page data without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Get recently created pages by a specific user in 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 getUserRecentPages: 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.
getUserRecentPages 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 getUserRecentPages 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 getUserRecentPages. 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.
getUserRecentPages 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 →