Low Risk

all_paths

Find all simple paths between two nodes. Fuzzy matches labels.

How to control all_paths ↓

What all_paths does on Mcp Graph Engine

AI agents call all_paths to retrieve information from Mcp Graph Engine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why all_paths needs a policy

The tool reads path data from the graph between two nodes using fuzzy label matching. It does not modify, delete, or execute anything; it purely retrieves relationship paths, making it a Read operation with low severity.

From the tool's definition "Find all simple paths between two nodes" — this is a graph traversal/query operation with no side effects.

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access all_paths gives an agent:

How to control all_paths

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Graph Engine, and nothing reaches the server without passing your rules. This is the rule we recommend for all_paths:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "all_paths": {}
  }
}

all_paths is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Graph Engine — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about all_paths

What does the all_paths tool do? +

Find all simple paths between two nodes. Fuzzy matches labels. It is categorised as a Read tool in the Mcp Graph Engine MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on all_paths? +

Register the Mcp Graph Engine MCP server in PolicyLayer and add a rule for all_paths: 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 Mcp Graph Engine. Nothing to install.

What risk level is all_paths? +

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

Can I rate-limit all_paths? +

Yes. Add a rate_limit block to the all_paths 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 all_paths completely? +

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

all_paths is provided by the Mcp Graph Engine MCP server (utilitydelta/mcp-graph-engine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Graph Engine tool call.

Start from Mcp Graph Engine, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

24 Mcp Graph Engine tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.