Find mementos that connect different clusters (knowledge bridges)
AI agents call get_central_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 performs a search/discovery operation over existing memento relationships to identify nodes that serve as connectors between clusters. It has no side effects, creates no new data, modifies nothing, and executes no external operations. It is purely informational—reading and analyzing the existing knowledge graph structure.
From the tool's definition Tool description states 'Find mementos that connect different clusters (knowledge bridges)' — a query operation that retrieves and identifies existing data relationships without modifying or deleting anything.
Attacks that exploit this kind of access
Find mementos that connect different clusters (knowledge bridges). 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_central_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_central_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_central_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_central_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_central_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 →