deeptrace_search_evidence

Full-text search across ingested evidence chunks. Returns matching chunks with relevance ranking, source URLs, and content hashes for provenance verification.

SERVERNodebench SOURCEnodebench-mcp

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-homenshum-nodebench/deeptrace-search-evidence.md

WHAT IT DOES

What deeptrace_search_evidence does on Nodebench

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

RISK

Why deeptrace_search_evidence is rated Low

This is a search/query tool that retrieves data without side effects. It searches pre-ingested content and returns results with metadata for verification purposes. The inclusion of 'source URLs' and 'content hashes for provenance verification' further confirms this is a read-only information retrieval function. No write, delete, execute, or financial capabilities are indicated.

From the tool's definition Tool performs 'Full-text search across ingested evidence chunks' with 'matching chunks' returned. The description indicates retrieval and querying operations only: 'Returns matching chunks with relevance ranking, source URLs, and content hashes.' No…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs deeptrace_search_evidence safely

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

deeptrace_search_evidence Allowed

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

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

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

FAQ

Questions about deeptrace_search_evidence

What does the deeptrace_search_evidence tool do? +

Full-text search across ingested evidence chunks. Returns matching chunks with relevance ranking, source URLs, and content hashes for provenance verification. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on deeptrace_search_evidence? +

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

What risk level is deeptrace_search_evidence? +

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

Can I rate-limit deeptrace_search_evidence? +

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

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

deeptrace_search_evidence is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

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