search_nodes

Search project entities and relations by query

SERVERProject Guardian MCP SOURCE1999azzar/project-guardian-mcp-server

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/1999azzar-project-guardian-mcp-server/search-nodes.md

WHAT IT DOES

What search_nodes does on Project Guardian MCP

AI agents call search_nodes to retrieve information from Project Guardian MCP 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

The tool retrieves or queries existing data from the knowledge graph without creating, modifying, deleting, or executing operations. It is a pure read operation. The query-based search mechanism may return results based on user input, but it does not change state.

From the tool's definition Tool name is 'search_nodes' and description states it 'Search project entities and relations by query' — these are information retrieval operations with no data modification.

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 Project Guardian MCP, 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 Project Guardian MCP, 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 project entities and relations by query. It is categorised as a Read tool in the Project Guardian MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_nodes? +

Register the Project Guardian 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 Project Guardian MCP. 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 Project Guardian MCP server (1999azzar/project-guardian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Project Guardian, and thousands of servers like it.

This server

All 36 Project Guardian tools →

Across the catalogue

evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server → The MCP Attack Database →

Guides

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