AI agents call aim_memory_get to retrieve information from Mcp Knowledge Graph without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries stored memory data without side effects. It does not create, modify, delete, or execute external operations—it only reads existing memory entries by name. This is a classic Read operation with minimal risk.
From the tool's definition Tool name 'aim_memory_get' and description 'Retrieve specific memories by exact name' indicate a retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access aim_memory_get 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_get:
{
"version": "1",
"default": "deny",
"tools": {
"aim_memory_get": {}
}
}aim_memory_get is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve specific memories by exact name. It is categorised as a Read tool in the Mcp Knowledge Graph MCP Server, which means it retrieves data without modifying state.
Register the Mcp Knowledge Graph MCP server in PolicyLayer and add a rule for aim_memory_get: 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.
aim_memory_get 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 aim_memory_get 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 aim_memory_get. 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.
aim_memory_get 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.
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.