record_provenance_receipt

Persist a durable execution receipt for a tool call, approval, verification, or other meaningful action.

SERVERNodebench SOURCEnodebench-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/record-provenance-receipt.md

What record_provenance_receipt does on Nodebench

AI agents use record_provenance_receipt to create or update resources in Nodebench, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nodebench environment.

Why record_provenance_receipt is rated Medium

The tool writes/stores a provenance receipt (audit record) permanently. This is a Write operation — it creates new data (a receipt) in a durable store. While 'durable' implies it may not be easily reversible, the action itself is additive (persisting a record) rather than destructive. Misuse could result in false or manipulated audit trails, giving it medium severity.

From the tool's definition Persist a durable execution receipt for a tool call, approval, verification, or other meaningful action.

Questions about record_provenance_receipt

What does the record_provenance_receipt tool do? +

Persist a durable execution receipt for a tool call, approval, verification, or other meaningful action. It is categorised as a Write tool in the Nodebench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on record_provenance_receipt? +

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

record_provenance_receipt is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit record_provenance_receipt? +

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

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

record_provenance_receipt 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Nodebench's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.