recompute_trustee_report_waterfall
Securitization Trustee-Report Waterfall Recomputation: OpenChainGraph compute node (analytics_mandate). Deterministic OpenChainGraph compute node. By default (compute:"auto") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:"browser" forc...
This record as markdown: /tools/postoaklabs-ainumbers-mcp-apps/recompute-trustee-report-waterfall.md
What recompute_trustee_report_waterfall does on Ainumbers Mcp Apps
AI agents call recompute_trustee_report_waterfall to retrieve information from Ainumbers Mcp Apps without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
compute | string | — | Compute mode (v0.4 Compute Binding). "auto" (default) = server for gpu:false nodes with registered kernels; "server" = force server-side; "browser" = always ret |
parent_hashes | array | — | execution_hash values from upstream ChainGraph AP2 artifacts to chain from (sets chain.parent_hashes in the export). |
parent_tool_ids | array | — | tool_id values matching parent_hashes, in the same order. |
policy_parameters | object | — | Input parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is "auto" or "serv |
Parameters from the server's own tool schema.
Why recompute_trustee_report_waterfall is rated Low
Deterministic financial analytics computation with no data modification, but involves trustee reporting and securitization domain complexity.
From the tool's definition Securitization Trustee-Report Waterfall Recomputation, deterministic compute node, analytics analytics_mandate
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs recompute_trustee_report_waterfall safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ainumbers Mcp Apps, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For recompute_trustee_report_waterfall, this is the rule to start with:
recompute_trustee_report_waterfall 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 Ainumbers Mcp Apps, apply this rule, and every recompute_trustee_report_waterfall call is checked against it from then on.
Questions about recompute_trustee_report_waterfall
Securitization Trustee-Report Waterfall Recomputation: OpenChainGraph compute node (analytics_mandate). Deterministic OpenChainGraph compute node. By default (compute:"auto") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:"browser" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use synthetic or anonymised inputs only. Exports an AP2 artifact with execution_hash for chain provenance. Open at: https://ainumbers.co/chaingraph/art-568-securitization-trustee-report-recompute.html FV-status (published/proven/still-trusted for this spec): /fv-status/565f2dd45a55e0ff0f8dafde8c1080f9e1484b32a5aaa96f4d7739a236b9258a.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Summary: Recomputes a securitization priority-of-payments waterfall for one stated distribution period from a caller-declared tier list and the period's own collections, then compares the recomputed distribution against what the monthly trustee report states was distributed. Outputs: citations, collections_by_type, comparison_basis, currency, deal_ref, diff, fence, first_unfunded_tier, indenture_ref, indeterminate_reason, minor_unit_exponent, not_proven, note, period_label, rationale, rejected_inputs, residual_by_type, residual_display, residual_minor_units, skipped_tier_count, tier_count, tiers, total_collections_display, total_collections_minor_units, total_paid_display, total_paid_minor_units, total_shortfall_display, total_shortfall_minor_units, triggers_evaluated, trustee_reported_supplied, verdict. Output schema: call describe_tool("recompute_trustee_report_waterfall"). It is categorised as a Read tool in the Ainumbers Mcp Apps MCP Server, which means it retrieves data without modifying state.
recompute_trustee_report_waterfall accepts 4 parameters: compute, parent_hashes, parent_tool_ids, policy_parameters. The full parameter table on this page comes from the server's own tool schema.
Register the Ainumbers Mcp Apps MCP server in PolicyLayer and add a rule for recompute_trustee_report_waterfall: 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 Ainumbers Mcp Apps. Nothing to install.
recompute_trustee_report_waterfall 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 recompute_trustee_report_waterfall 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 recompute_trustee_report_waterfall. 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.
recompute_trustee_report_waterfall is provided by the Ainumbers Mcp Apps MCP server (postoaklabs/ainumbers-mcp-apps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ainumbers Mcp Apps, and thousands of servers like it.
This server
Across the catalogue