List graph edges, optionally constrained to an entity and direction.
AI agents call list_relationships to retrieve information from SQLite Project Memory 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 existing relationship data from the graph without creating, modifying, or deleting any entities or relationships. It is a passive read operation constrained by optional filters, making it a straightforward Read category tool with low severity.
From the tool's definition Tool name 'list_relationships' and description 'List graph edges, optionally constrained to an entity and direction' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List graph edges, optionally constrained to an entity and direction. It is categorised as a Read tool in the SQLite Project Memory MCP MCP Server, which means it retrieves data without modifying state.
Register the SQLite Project Memory MCP server in PolicyLayer and add a rule for list_relationships: 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 SQLite Project Memory MCP. Nothing to install.
list_relationships 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_relationships 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_relationships. 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_relationships is provided by the SQLite Project Memory MCP server (webrtcgame/sqlite-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 →