Get all relationships for an entity in the knowledge graph. Args: entity: The entity name to look up. Returns all edges (relationships) connected to this entity.
AI agents call entity_edges to retrieve information from Yantrikdb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query/retrieval operation with no side effects. The tool reads knowledge graph structure to answer questions about entity relationships, fitting the Read category. Severity is low because unauthorized access to relationship metadata poses minimal risk compared to modification or deletion of knowledge, and the blast radius of misuse (returning existing data) is constrained.
From the tool's definition Tool retrieves relationships from a knowledge graph ('Get all relationships for an entity', 'Returns all edges'). No modification, deletion, or execution is performed—it only queries and returns data about existing relationships.
Documented attack patterns abuse exactly the kind of access entity_edges gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Yantrikdb, and nothing reaches the server without passing your rules. This is the rule we recommend for entity_edges:
{
"version": "1",
"default": "deny",
"tools": {
"entity_edges": {}
}
}entity_edges is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all relationships for an entity in the knowledge graph. Args: entity: The entity name to look up. Returns all edges (relationships) connected to this entity. It is categorised as a Read tool in the Yantrikdb MCP Server, which means it retrieves data without modifying state.
Register the Yantrikdb MCP server in PolicyLayer and add a rule for entity_edges: 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 Yantrikdb. Nothing to install.
entity_edges 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 entity_edges 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 entity_edges. 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.
entity_edges is provided by the Yantrikdb MCP server (yantrikos/yantrikdb-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Yantrikdb tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Yantrikdb tools catalogued and risk-classified — across an index of 42,500+ MCP servers.