Low Risk

memory_get_relations

GET RELATIONS SHOW LINKS - Get all relationships for a specific memory. Keywords: get relations, show links, list connections, view relationships, find associations

How to control memory_get_relations ↓

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

Low Risk

This tool retrieves and displays existing relationship data associated with a memory without modifying, deleting, or executing external operations. It is purely informational and has no side effects. The action verbs (get, show, list, view, find) all indicate read-only operations. Severity is low because reading memory relationships poses minimal risk even if queried inappropriately by an agent.

From the tool's definition Tool name 'memory_get_relations' and description explicitly states 'GET RELATIONS SHOW LINKS' and 'Get all relationships for a specific memory.' Keywords include 'get relations', 'show links', 'list connections', 'view relationships', 'find associations'—all…

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

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

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

memory_get_relations 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 MCP AI Memory — 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.

Go deeper

What does the memory_get_relations tool do? +

GET RELATIONS SHOW LINKS - Get all relationships for a specific memory. Keywords: get relations, show links, list connections, view relationships, find associations. It is categorised as a Read tool in the MCP AI Memory MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_get_relations? +

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

What risk level is memory_get_relations? +

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

Can I rate-limit memory_get_relations? +

Yes. Add a rate_limit block to the memory_get_relations 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 memory_get_relations completely? +

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

memory_get_relations is provided by the MCP AI Memory MCP server (scanadi/mcp-ai-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP AI Memory tool call.

Deterministic rules across all 17 MCP AI Memory tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

17 MCP AI Memory tools catalogued and risk-classified — across an index of 42,500+ 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.