find_related
A read tool on the Agent Store MCP server.
This record as markdown: /tools/agent-store/find-related.md
What find_related does on Agent Store
AI agents call find_related to retrieve information from Agent Store without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why find_related is rated Low
The name 'find_related' most naturally implies a search or lookup operation that retrieves associated data without modifying state. This aligns with the Read category. However, the empty description and lack of parameter details create uncertainty. The sibling tools (gbrain_search, gbrain_query, gbrain_get_page, gbrain_list_pages) are all Read operations, suggesting this server is query-focused.
From the tool's definition Tool name 'find_related' suggests retrieval or query of related items; description is empty, limiting confidence in classification.
Attacks that exploit this kind of access
The rule that runs find_related safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agent Store, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_related, this is the rule to start with:
find_related is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Agent Store, apply this rule, and every find_related call is checked against it from then on.
Questions about find_related
find_related is a read tool on the Agent Store MCP server. It is categorised as a Read tool in the Agent Store MCP Server, which means it retrieves data without modifying state.
Register the Agent Store MCP server in PolicyLayer and add a rule for find_related: 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 Agent Store. Nothing to install.
find_related 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 find_related 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 find_related. 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.
find_related is provided by the Agent Store MCP server (chrisluersen/agent-store). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agent Store, and thousands of servers like it.
This server
Across the catalogue