List graphs owned by the authenticated user.
AI agents call list_graphs to retrieve information from Mnemosyne MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about graphs belonging to the authenticated user. It performs a read-only operation with no capacity to modify, delete, or execute code. The blast radius of misuse is minimal—an attacker could at most enumerate the user's knowledge graphs, which is a low-severity information disclosure. The OAuth authentication requirement provides additional protection.
From the tool's definition Tool name 'list_graphs' and description 'List graphs owned by the authenticated user' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List graphs owned by the authenticated user. It is categorised as a Read tool in the Mnemosyne MCP MCP Server, which means it retrieves data without modifying state.
Register the Mnemosyne MCP server in PolicyLayer and add a rule for list_graphs: 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 Mnemosyne MCP. Nothing to install.
list_graphs 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 list_graphs 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 list_graphs. 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.
list_graphs is provided by the Mnemosyne MCP server (sophia-labs/mnemosyne-mcp). 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 →