deeptrace_receipt_stats

Get aggregate statistics across all receipts — total count, policy action breakdown, top agents, and top tools.

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-receipt-stats.md

WHAT IT DOES

What deeptrace_receipt_stats does on Nodebench

AI agents call deeptrace_receipt_stats 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_receipt_stats is rated Low

The tool performs read-only queries on receipt data to generate summary statistics. It uses standard analytical operations (count, grouping, sorting) without modifying, deleting, or executing external operations. This is a straightforward data retrieval use case with minimal blast radius.

From the tool's definition Tool retrieves aggregate statistics across receipts with operations limited to counting, breakdown analysis, and ranking (top agents, top tools). No mutations, deletions, or external side effects described.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs deeptrace_receipt_stats 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_receipt_stats, this is the rule to start with:

deeptrace_receipt_stats Allowed

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

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_receipt_stats call is checked against it from then on.

FAQ

Questions about deeptrace_receipt_stats

What does the deeptrace_receipt_stats tool do? +

Get aggregate statistics across all receipts — total count, policy action breakdown, top agents, and top tools. 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_receipt_stats? +

Register the Nodebench MCP server in PolicyLayer and add a rule for deeptrace_receipt_stats: 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_receipt_stats? +

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

Can I rate-limit deeptrace_receipt_stats? +

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

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

deeptrace_receipt_stats 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

The MCP Attack Database →

Guides

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