AI agents call memory_graph to retrieve information from Tages without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads existing cross-system references stored in memory and generates a Mermaid diagram visualization. It only retrieves and transforms data into a graph representation without creating, modifying, or deleting any data.
From the tool's definition Build a relationship graph from crossSystemRefs and output as a Mermaid diagram
Attacks that exploit this kind of access
Build a relationship graph from crossSystemRefs and output as a Mermaid diagram. It is categorised as a Read tool in the Tages MCP Server, which means it retrieves data without modifying state.
Register the Tages MCP server in PolicyLayer and add a rule for memory_graph: 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 Tages. Nothing to install.
memory_graph 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 memory_graph 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 memory_graph. 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.
memory_graph is provided by the Tages MCP server (ryantlee25-droid/tages). 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 →