Medium Risk

aim_memory_link

Link two memories together

How to control aim_memory_link ↓

AI agents use aim_memory_link to create or update resources in Mcp Knowledge Graph — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Knowledge Graph environment.

Medium Risk

This tool creates a relationship/association between two existing memory nodes in the knowledge graph. It modifies the graph structure by adding edges/links between nodes, which is a reversible write operation. It does not delete data, execute code, or involve financial transactions.

From the tool's definition Link two memories together

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "aim_memory_link": {
      "limits": [
        {
          "counter": "aim_memory_link_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

aim_memory_link stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Knowledge Graph — 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.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the aim_memory_link tool do? +

Link two memories together. It is categorised as a Write tool in the Mcp Knowledge Graph MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on aim_memory_link? +

Register the Mcp Knowledge Graph MCP server in PolicyLayer and add a rule for aim_memory_link: 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 Knowledge Graph. Nothing to install.

What risk level is aim_memory_link? +

aim_memory_link is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit aim_memory_link? +

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

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

aim_memory_link is provided by the Mcp Knowledge Graph MCP server (shaneholloman/mcp-knowledge-graph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Knowledge Graph tool call.

Deterministic rules across all 10 Mcp Knowledge Graph tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

10 Mcp Knowledge Graph 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.