Low Risk

list_graphs

Discover available knowledge graphs and their schemas, including node types, relationship types, and versions. Use this tool first to find valid graphId values for other tools.

Part of the Fodda Knowledge Graphs server.

list_graphs is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE FODDA KNOWLEDGE GRAPHS →

Free to start. No card required.

AI agents call list_graphs to retrieve information from Fodda Knowledge Graphs 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.

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

See the full Fodda Knowledge Graphs policy for all 8 tools.

Get this rule live on your own Fodda Knowledge Graphs server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY FODDA KNOWLEDGE GRAPHS →

These attack patterns abuse exactly the kind of access list_graphs gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so list_graphs only ever does what you allow.

SECURE FODDA KNOWLEDGE GRAPHS →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the list_graphs tool do? +

Discover available knowledge graphs and their schemas, including node types, relationship types, and versions. Use this tool first to find valid graphId values for other tools.. It is categorised as a Read tool in the Fodda Knowledge Graphs MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_graphs? +

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

What risk level is list_graphs? +

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

Can I rate-limit list_graphs? +

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

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

What MCP server provides list_graphs? +

list_graphs is provided by the Fodda Knowledge Graphs MCP server (fodda/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Fodda Knowledge Graphs tool call.

Deterministic rules across all 8 Fodda Knowledge Graphs tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.