Low Risk

find_related_memories

Find memories related through graph traversal

How to control find_related_memories ↓

What find_related_memories does on AGI MCP Server

AI agents call find_related_memories to retrieve information from AGI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why find_related_memories needs a policy

This tool performs graph traversal to discover and retrieve related memories—a read-only operation with no side effects. It queries the memory graph structure but does not create, modify, or delete any data. The blast radius of misuse is minimal; worst case, an agent retrieves unintended memory data, but no irreversible changes occur.

From the tool's definition Tool name 'find_related_memories' and description 'Find memories related through graph traversal' indicate a query/search operation that traverses relationships to retrieve existing memory data without modification.

Documented attack patterns abuse exactly the kind of access find_related_memories gives an agent:

How to control find_related_memories

PolicyLayer is an MCP gateway — it sits between your AI agents and AGI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for find_related_memories:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_related_memories": {}
  }
}

find_related_memories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register AGI MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about find_related_memories

What does the find_related_memories tool do? +

Find memories related through graph traversal. It is categorised as a Read tool in the AGI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_related_memories? +

Register the AGI MCP Server MCP server in PolicyLayer and add a rule for find_related_memories: 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 AGI MCP Server. Nothing to install.

What risk level is find_related_memories? +

find_related_memories is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_related_memories? +

Yes. Add a rate_limit block to the find_related_memories 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.

How do I block find_related_memories completely? +

Set action: deny in the PolicyLayer policy for find_related_memories. 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.

What MCP server provides find_related_memories? +

find_related_memories is provided by the AGI MCP Server MCP server (quixiai/agi-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AGI MCP Server tool call.

Start from AGI MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

24 AGI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.