storage_charge_epoch
Run one proof-of-retrievability-gated charge epoch for a storage deal.
This record as markdown: /tools/network-tenzro-tenzro/storage-charge-epoch.md
What storage_charge_epoch does on Tenzro Ledger MCP
AI agents use storage_charge_epoch to commit financial operations through Tenzro Ledger MCP, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why storage_charge_epoch is rated Critical
This tool executes a billing/charge cycle for a storage deal, which constitutes committing a financial obligation or moving funds. The phrase 'charge epoch' directly implies a payment or fee collection event.
From the tool's definition 'charge epoch for a storage deal' — triggers a financial charging event gated on proof-of-retrievability
Attacks that exploit this kind of access
The rule that runs storage_charge_epoch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tenzro Ledger MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For storage_charge_epoch, this is the rule to start with:
Any call to storage_charge_epoch is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every storage_charge_epoch call is checked against it from then on.
Questions about storage_charge_epoch
Run one proof-of-retrievability-gated charge epoch for a storage deal. It is categorised as a Financial tool in the Tenzro Ledger MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for storage_charge_epoch: 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 Tenzro Ledger MCP. Nothing to install.
storage_charge_epoch is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the storage_charge_epoch 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 storage_charge_epoch. 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.
storage_charge_epoch is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tenzro Ledger, and thousands of servers like it.
Across the catalogue