search_nodes · MCP DuckDB Knowledge Graph Memory Server MCP

WHAT IT DOES

What search_nodes does on MCP DuckDB Knowledge Graph Memory Server

AI agents call search_nodes to retrieve information from MCP DuckDB Knowledge Graph Memory Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why search_nodes needs a policy

The tool searches and retrieves nodes from a knowledge graph without creating, modifying, or deleting data. It has no side effects and only performs a query operation, which is characteristic of a Read category tool. The low severity reflects minimal risk if misused—an AI agent could only retrieve existing data, not cause harm through this tool alone.

From the tool's definition Tool name 'search_nodes' and description 'Search for nodes in the knowledge graph based on a query' indicate retrieval functionality without modification.

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

POLICY

How to control search_nodes

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP DuckDB Knowledge Graph Memory Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_nodes:

policy.json

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

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

Create a free account and register MCP DuckDB Knowledge Graph Memory Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP DuckDB Knowledge Graph Memory Server tools

Destructive delete_entities Delete multiple entities and their associated relations from the knowledge graph Destructive delete_observations Delete specific observations from entities in the knowledge graph Destructive delete_relations Delete multiple relations from the knowledge graph Write add_observations Add new observations to existing entities in the knowledge graph Write create_entities Create multiple new entities in the knowledge graph Write create_relations Create multiple new relations between entities in the knowledge graph. Relations should be Read open_nodes Open specific nodes in the knowledge graph by their names

All 8 MCP DuckDB Knowledge Graph Memory Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about search_nodes

What does the search_nodes tool do? +

Search for nodes in the knowledge graph based on a query. It is categorised as a Read tool in the MCP DuckDB Knowledge Graph Memory Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_nodes? +

Register the MCP DuckDB Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for search_nodes: 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 DuckDB Knowledge Graph Memory Server. Nothing to install.

What risk level is search_nodes? +

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

Can I rate-limit search_nodes? +

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

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

search_nodes is provided by the MCP DuckDB Knowledge Graph Memory Server MCP server (izumisy/mcp-duckdb-memory-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP DuckDB Knowledge Graph Memory Server tool call.

Start from MCP DuckDB Knowledge Graph Memory Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

8 MCP DuckDB Knowledge Graph Memory Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.