Search pages in GROWI using Elasticsearch
AI agents call searchPages 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 searches and retrieves page information from a wiki system. Searching is a non-destructive read operation with no side effects—it does not create, modify, delete, or execute actions. The confidence is high because the description explicitly uses 'Search' which is a classic read operation.
From the tool's definition Tool name 'searchPages' and description 'Search pages in GROWI using Elasticsearch' indicate a query operation that retrieves data without modification.
Attacks that exploit this kind of access
Search pages in GROWI using Elasticsearch. 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 searchPages: 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.
searchPages 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 searchPages 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 searchPages. 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.
searchPages 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 →