get_related_mementos
AI agents call get_related_mementos to retrieve information from MCP Memento without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves related mementos from the knowledge base—a read operation with no side effects. While the empty description reduces confidence slightly, the name structure and server context strongly suggest a query function. No data is created, modified, or deleted; it merely returns information. Severity is low because misuse would only expose existing stored information without enabling damage.
From the tool's definition Tool name 'get_related_mementos' indicates a retrieval operation. The description is empty, but the naming pattern aligns with other read-only tools on this server like 'contextual_memento_search' and 'find_memento_patterns', which query the persistent memory…
Attacks that exploit this kind of access
get_related_mementos. It is categorised as a Read tool in the MCP Memento MCP Server, which means it retrieves data without modifying state.
Register the MCP Memento MCP server in PolicyLayer and add a rule for get_related_mementos: 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 Memento. Nothing to install.
get_related_mementos 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_related_mementos 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_related_mementos. 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_related_mementos is provided by the MCP Memento MCP server (x-hannibal/mcp-memento). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →