Search for tags in GROWI
AI agents call searchTags 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 search operation to retrieve tags from the GROWI wiki system. Search operations are read-only and do not create, modify, delete, or execute any actions. No data is changed, and the blast radius of misuse is minimal—an agent could only retrieve existing tag information. This is a straightforward Read category tool.
From the tool's definition Tool name 'searchTags' and description 'Search for tags in GROWI' indicate a query operation that retrieves tag data without modification or side effects.
Attacks that exploit this kind of access
Search for tags 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 searchTags: 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.
searchTags 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 searchTags 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 searchTags. 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.
searchTags 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 →