extract_and_split_receipt
Extract line items from a receipt image, assign them to people using an assignment prompt, and automatically split the bill to create real debt records.
This record as markdown: /tools/nitrostack/extract-and-split-receipt.md
What extract_and_split_receipt does on Nitrostack
AI agents use extract_and_split_receipt to commit financial operations through Nitrostack, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why extract_and_split_receipt is rated Critical
Tool creates real financial debt records by splitting bills among people.
From the tool's definition split the bill to create real debt records
Attacks that exploit this kind of access
The rule that runs extract_and_split_receipt safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For extract_and_split_receipt, this is the rule to start with:
Any call to extract_and_split_receipt is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Nitrostack, apply this rule, and every extract_and_split_receipt call is checked against it from then on.
Questions about extract_and_split_receipt
Extract line items from a receipt image, assign them to people using an assignment prompt, and automatically split the bill to create real debt records. It is categorised as a Financial tool in the Nitrostack MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Nitrostack MCP server in PolicyLayer and add a rule for extract_and_split_receipt: 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 Nitrostack. Nothing to install.
extract_and_split_receipt 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 extract_and_split_receipt 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 extract_and_split_receipt. 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.
extract_and_split_receipt is provided by the Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nitrostack, and thousands of servers like it.
Across the catalogue