Find related entities through relationship traversal
AI agents call find_related_entities to retrieve information from ZMCPTools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries relational data through graph traversal. It performs no modifications, deletions, or external operations. The capability to traverse relationships in a knowledge graph or database is fundamentally a Read operation with minimal blast radius if misused by an autonomous agent—it simply returns data without altering state.
From the tool's definition Tool name 'find_related_entities' and description 'Find related entities through relationship traversal' indicate a query/lookup operation. The verb 'find' and the absence of any modification language (create, update, delete) confirm read-only intent.
Documented attack patterns abuse exactly the kind of access find_related_entities gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ZMCPTools, and nothing reaches the server without passing your rules. This is the rule we recommend for find_related_entities:
{
"version": "1",
"default": "deny",
"tools": {
"find_related_entities": {}
}
}find_related_entities 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.
Find related entities through relationship traversal. It is categorised as a Read tool in the ZMCPTools MCP Server, which means it retrieves data without modifying state.
Register the ZMCPTools MCP server in PolicyLayer and add a rule for find_related_entities: 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 ZMCPTools. Nothing to install.
find_related_entities 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_related_entities 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_related_entities. 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_related_entities is provided by the ZMCPTools MCP server (zachhandley/zmcptools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 70 ZMCPTools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
70 ZMCPTools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.