search_nodes

Search for nodes in the knowledge graph based on a query

SERVERCowork Bench SOURCE0717376/cowork_bench

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/cowork-bench/search-nodes.md

WHAT IT DOES

What search_nodes does on Cowork Bench

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

RISK

Why search_nodes is rated Low

This tool performs a read-only search operation on a knowledge graph. It retrieves or queries data without any side effects, creation, modification, deletion, or execution of code/commands. The action is passive information retrieval, fitting the 'Read' category. The severity is low as misuse would only result in unauthorized information access, not destructive or executable harm.

From the tool's definition Tool name 'search_nodes' combined with description 'Search for nodes in the knowledge graph based on a query' indicates a retrieval/query operation with no modification or execution of external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_nodes safely

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

search_nodes Allowed

search_nodes 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": {
    "search_nodes": {}
  }
}

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

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

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 Cowork Bench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_nodes? +

Register the Cowork Bench 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 Cowork Bench. 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 Cowork Bench MCP server (0717376/cowork_bench). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cowork Bench, and thousands of servers like it.

This server

All 433 Cowork Bench tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

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