deeptrace_get_evidence_pack
Retrieve an evidence pack by ID, including all its constituent chunks with full content and provenance metadata.
This record as markdown: /tools/io-github-homenshum-nodebench/deeptrace-get-evidence-pack.md
What deeptrace_get_evidence_pack does on Nodebench
AI agents call deeptrace_get_evidence_pack 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.
Why deeptrace_get_evidence_pack is rated Low
This is a read operation that queries and returns an evidence pack and its constituent data. While the severity is elevated to 'medium' rather than 'low' due to the tool being part of a large server (260 MCP tools) with access to research/investigation data that could include sensitive information, and the potential for an agent to misuse retrieved evidence in harmful ways, the tool itself performs no modifications,…
From the tool's definition Tool description states 'Retrieve an evidence pack by ID' - retrieves data with no side effects. Returns 'chunks with full content and provenance metadata'.
Attacks that exploit this kind of access
The rule that runs deeptrace_get_evidence_pack 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_get_evidence_pack, this is the rule to start with:
deeptrace_get_evidence_pack is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every deeptrace_get_evidence_pack call is checked against it from then on.
Questions about deeptrace_get_evidence_pack
Retrieve an evidence pack by ID, including all its constituent chunks with full content and provenance metadata. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for deeptrace_get_evidence_pack: 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.
deeptrace_get_evidence_pack is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the deeptrace_get_evidence_pack 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.
Set action: deny in the PolicyLayer policy for deeptrace_get_evidence_pack. 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.
deeptrace_get_evidence_pack 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.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue