find_entity_path

Find the shortest path between two entities in the knowledge graph. Returns the complete path, path length, and relationship details for each connection. Useful for discovering how concepts are related and understanding knowledge connections.

Server TDZ C64 Knowledge michaeltroelsen/tdz-c64-knowledge
Category Read
Risk class Low
Parameters 00 required

What find_entity_path does on TDZ C64 Knowledge

AI agents call find_entity_path to retrieve information from TDZ C64 Knowledge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why find_entity_path needs a policy

This is a graph traversal and query tool that retrieves pre-existing relationship data from the knowledge graph. It performs no writes, deletions, or external executions—only navigation and read access to documented entity relationships. The blast radius of misuse is minimal (information disclosure only).

From the tool's definition Tool finds and returns 'the shortest path between two entities', 'path length', and 'relationship details' — purely retrieval operations with no modification or side effects.

Questions about find_entity_path

What does the find_entity_path tool do? +

Find the shortest path between two entities in the knowledge graph. Returns the complete path, path length, and relationship details for each connection. Useful for discovering how concepts are related and understanding knowledge connections. It is categorised as a Read tool in the TDZ C64 Knowledge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_entity_path? +

Register the TDZ C64 Knowledge MCP server in PolicyLayer and add a rule for find_entity_path: 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 TDZ C64 Knowledge. Nothing to install.

What risk level is find_entity_path? +

find_entity_path is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_entity_path? +

Yes. Add a rate_limit block to the find_entity_path 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.

How do I block find_entity_path completely? +

Set action: deny in the PolicyLayer policy for find_entity_path. 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.

What MCP server provides find_entity_path? +

find_entity_path is provided by the TDZ C64 Knowledge MCP server (michaeltroelsen/tdz-c64-knowledge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.