agent_graph_list

List agent graphs with node status, placement, and summaries.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/agent-graph-list.md

WHAT IT DOES

What agent_graph_list does on Yaver

AI agents call agent_graph_list to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why agent_graph_list is rated Low

Tool queries and retrieves agent graph metadata without modifying or executing operations.

From the tool's definition List agent graphs with node status, placement, and summaries.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs agent_graph_list safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agent_graph_list, this is the rule to start with:

agent_graph_list Allowed

agent_graph_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "agent_graph_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every agent_graph_list call is checked against it from then on.

FAQ

Questions about agent_graph_list

What does the agent_graph_list tool do? +

List agent graphs with node status, placement, and summaries. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on agent_graph_list? +

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

What risk level is agent_graph_list? +

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

Can I rate-limit agent_graph_list? +

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

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

agent_graph_list is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 664 Yaver tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →get_agent on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →