AI agents call get to retrieve information from My Memory 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 (entities, observations, relationships) without creating, modifying, or deleting information. It is a read-only operation with no side effects.
From the tool's definition Tool name 'get' and description '엔티티/관찰/관계 목록 조회' (list retrieval of entities/observations/relationships) indicate data retrieval without modification.
Attacks that exploit this kind of access
엔티티/관찰/관계 목록 조회. It is categorised as a Read tool in the My Memory MCP Server, which means it retrieves data without modifying state.
Register the My Memory MCP server in PolicyLayer and add a rule for 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 My Memory. Nothing to install.
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 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 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.
get is provided by the My Memory MCP server (moontmsai/my-memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get is one line of My Memory's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →