resolve_ref
Resolve a stable alias (ref) to its entity name via the RefIndex
This record as markdown: /tools/danielsimonjr-memory-mcp/resolve-ref.md
What resolve_ref does on Enhanced Knowledge Graph Memory Server
AI agents call resolve_ref to retrieve information from Enhanced Knowledge Graph Memory Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why resolve_ref is rated Low
This tool performs a lookup/resolution operation - translating an alias to an entity name. It only reads from the RefIndex with no side effects, data creation, or modification.
From the tool's definition Resolve a stable alias (ref) to its entity name via the RefIndex
Attacks that exploit this kind of access
The rule that runs resolve_ref safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For resolve_ref, this is the rule to start with:
resolve_ref 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 Enhanced Knowledge Graph Memory Server, apply this rule, and every resolve_ref call is checked against it from then on.
Questions about resolve_ref
Resolve a stable alias (ref) to its entity name via the RefIndex. It is categorised as a Read tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for resolve_ref: 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 Enhanced Knowledge Graph Memory Server. Nothing to install.
resolve_ref 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 resolve_ref 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 resolve_ref. 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.
resolve_ref is provided by the Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.
Across the catalogue