List all knowledge graphs with support for filtering by status and type. This is the main tool for getting information about existing graphs and an important path for obtaining node IDs. Use cases: 1. View all available graphs and their basic information 2. Get the node list of a specific graph f...
Single-target operation
Part of the Knowledge Graph Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call list_graphs to retrieve information from Knowledge Graph Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though list_graphs only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
list_graphs:
rules:
- action: allowSee the full Knowledge Graph Server policy for all 15 tools.
Agents calling read-class tools like list_graphs have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
List all knowledge graphs with support for filtering by status and type. This is the main tool for getting information about existing graphs and an important path for obtaining node IDs. Use cases: 1. View all available graphs and their basic information 2. Get the node list of a specific graph for subsequent edge addition or node detail queries 3. Filter graphs by status, such as viewing all drafts or published graphs 4. Filter graphs by type, such as viewing only topology or timeline graphs Usage recommendations: 1. First call this tool to get the graph list and node information 2. Get the required graph ID and node ID from the returned data 3. Use these IDs to call other tools (like add_edge, get_node_details) 4. Recommended to use this tool to confirm the target graph's status before performing any node or edge operations Return data: - data: List of graphs, each graph contains: * id: Graph ID (used for graphId parameter in other tools) * name: Graph name * description: Graph description * type: Graph type * status: Graph status * nodesCount: Number of nodes * edgesCount: Number of edges * createdAt: Creation time * updatedAt: Update time * publishedAt: Publication time (if published) * nodes: Node list, each node contains: - id: Node ID (used for add_edge and get_node_details tools) - name: Node name - type: Node type. It is categorised as a Read tool in the Knowledge Graph Server MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for list_graphs. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Knowledge Graph Server MCP server.
list_graphs 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 list_graphs rule in your Intercept 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 Intercept policy for list_graphs. 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.
list_graphs is provided by the Knowledge Graph Server MCP server (aiuluna/knowledge-graph-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept