recon_match
Parses a camt.053.001 statement (same schema-subset checks as camt053_parse) and a counterpart expectation set (CSV, header EndToEndId,Amount,Currency,Date -- same strict RFC 4180 parser as the WORKBOOK-1 CSV tools), then runs the SAME deterministic match engine as the tools/565 browser workbench...
This record as markdown: /tools/postoaklabs-ainumbers-mcp-apps/recon-match.md
What recon_match does on Ainumbers Mcp Apps
AI agents use recon_match to create or update resources in Ainumbers Mcp Apps, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ainumbers Mcp Apps environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
statement_xml | string | Yes | camt.053.001 XML statement document text. |
amount_tolerance | number | — | Absolute amount-match tolerance (default 0.01). |
expectations_csv | string | Yes | Counterpart expectations, CSV with header EndToEndId,Amount,Currency,Date. |
date_tolerance_days | number | — | Date-match tolerance in days (default 0). |
Parameters from the server's own tool schema.
Why recon_match is rated Medium
An AI agent can call recon_match faster than any human can review: one bad instruction and it creates or modifies resources in Ainumbers Mcp Apps by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs recon_match 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 recon_match, this is the rule to start with:
recon_match stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 recon_match call is checked against it from then on.
Questions about recon_match
Parses a camt.053.001 statement (same schema-subset checks as camt053_parse) and a counterpart expectation set (CSV, header EndToEndId,Amount,Currency,Date -- same strict RFC 4180 parser as the WORKBOOK-1 CSV tools), then runs the SAME deterministic match engine as the tools/565 browser workbench: EndToEndId exact match first (statement order), then amount+date tolerance + currency match (first unmatched expectation in CSV order). Returns matches, exceptions (unmatched entries/expectations), and a reconciliation receipt (statement digest, expectation-set digest, match-rule declaration, counts, exception digests, execution_hash) -- byte-identical to the browser tool for the same inputs. Prepare/hash/receipt only; per-exception disposition receipts are the browser workbench's interactive follow-on. It is categorised as a Write tool in the Ainumbers Mcp Apps MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
recon_match accepts 4 parameters: statement_xml, amount_tolerance, expectations_csv, date_tolerance_days. Required: statement_xml, expectations_csv. 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 recon_match: 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.
recon_match is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the recon_match 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 recon_match. 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.
recon_match 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