servicing_compliance_clock
Servicing Compliance Clock: OpenChainGraph compute node (consumer_finance). 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...
This record as markdown: /tools/postoaklabs-ainumbers-mcp-apps/servicing-compliance-clock.md
What servicing_compliance_clock does on Ainumbers Mcp Apps
AI agents call servicing_compliance_clock to permanently remove resources in Ainumbers Mcp Apps, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| 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 servicing_compliance_clock is rated Critical
An AI agent that decides to call servicing_compliance_clock doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Ainumbers Mcp Apps is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs servicing_compliance_clock 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 servicing_compliance_clock, this is the rule to start with:
servicing_compliance_clock is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ainumbers Mcp Apps, apply this rule, and every servicing_compliance_clock call is checked against it from then on.
Questions about servicing_compliance_clock
Servicing Compliance Clock: OpenChainGraph compute node (consumer_finance). 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/733-servicing-compliance-clock.html FV-status (published/proven/still-trusted for this spec): /fv-status/27ceec007c8035426d8ad4b2ade603d763c5b223d5a2e86369e7c27af06fca2b.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Summary: Computes servicer-compliance due dates and clock states from event dates and loan values across the Regulation X/Z servicing rules: error-resolution, information-request, loss-mitigation, foreclosure-timeline, force-placed-insurance, reminder, cancel, refund, payment-crediting, payoff-statement a... Outputs: verdict, obligations, evidence, manual_review_required. Output schema: call describe_tool("servicing_compliance_clock"). It is categorised as a Destructive tool in the Ainumbers Mcp Apps MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
servicing_compliance_clock 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 servicing_compliance_clock: 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.
servicing_compliance_clock is a Destructive 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 servicing_compliance_clock 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 servicing_compliance_clock. 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.
servicing_compliance_clock 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.
Across the catalogue