Find connections between entities in the knowledge graph
AI agents call find_connections to retrieve information from r3 (Recall) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches for and returns relationships between entities in an existing knowledge graph. It performs a semantic lookup operation without creating, modifying, deleting, or executing any external code. The action is purely informational retrieval, making it a Read category risk with low severity.
From the tool's definition Tool name 'find_connections' and description 'Find connections between entities in the knowledge graph' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Find connections between entities in the knowledge graph. It is categorised as a Read tool in the r3 (Recall) MCP Server, which means it retrieves data without modifying state.
Register the r3 (Recall) MCP server in PolicyLayer and add a rule for find_connections: 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 r3 (Recall). Nothing to install.
find_connections 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 find_connections 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 find_connections. 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.
find_connections is provided by the r3 (Recall) MCP server (n3wth/r3). 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 →