classify_mla_charge_inclusion
MLA Charge-Inclusion Classifier: OpenChainGraph compute node (compliance_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 execut...
This record as markdown: /tools/postoaklabs-ainumbers-mcp-apps/classify-mla-charge-inclusion.md
What classify_mla_charge_inclusion does on Ainumbers Mcp Apps
AI agents use classify_mla_charge_inclusion to commit financial operations through Ainumbers Mcp Apps, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| 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 classify_mla_charge_inclusion is rated Critical
classify_mla_charge_inclusion moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Attacks that exploit this kind of access
The rule that runs classify_mla_charge_inclusion 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 classify_mla_charge_inclusion, this is the rule to start with:
Any call to classify_mla_charge_inclusion is blocked until a human approves 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 classify_mla_charge_inclusion call is checked against it from then on.
Questions about classify_mla_charge_inclusion
MLA Charge-Inclusion Classifier: OpenChainGraph compute node (compliance_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-615-mla-charge-inclusion-classifier.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: Closed-set lookup of whether a charge type must be included in the Military Lending Act MAPR under 32 CFR 232.4(c) and 232.4(d). Outputs: charge_type, is_credit_card_account, short_term_exception_claimed, included_in_mapr, citation, basis, conditional_limit_usd, manual_review_required, manual_review_reason. Output schema: call describe_tool("classify_mla_charge_inclusion"). It is categorised as a Financial tool in the Ainumbers Mcp Apps MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
classify_mla_charge_inclusion 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 classify_mla_charge_inclusion: 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.
classify_mla_charge_inclusion 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 classify_mla_charge_inclusion 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 classify_mla_charge_inclusion. 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.
classify_mla_charge_inclusion 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