Stages Odoo transactions as DRAFT (unaccepted) vouchers in Tally Prime. Fetches invoices/journal entries from Odoo and maps them to correct Tally voucher type: Sales (out_invoice), Credit Note (out_refund), Purchase (in_invoice), Purchase Credit Note (in_refund), Journal/Payment/Receipt/Contra (j...
AI agents use push_voucher_draft to create or update resources in Tally Prime MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tally Prime MCP Server environment.
This tool creates and modifies financial data (vouchers, potentially master records) in Tally Prime, a financial ERP system. It is Write rather than Destructive because: (1) all vouchers are created in DRAFT/unaccepted state, not final/posted state, (2) drafts are reversible and explicitly require finance team acceptance, (3) no deletion or irreversible overwrites occur.
From the tool's definition Tool description states it 'Stages...as DRAFT (unaccepted) vouchers' and 'creates' vouchers with 'ISACCEPTED=No'. The operation is reversible: vouchers remain in DRAFT state until finance team accepts them, and drafts can be discarded.
Attacks that exploit this kind of access
Stages Odoo transactions as DRAFT (unaccepted) vouchers in Tally Prime. Fetches invoices/journal entries from Odoo and maps them to correct Tally voucher type: Sales (out_invoice), Credit Note (out_refund), Purchase (in_invoice), Purchase Credit Note (in_refund), Journal/Payment/Receipt/Contra (journal entries). ALL vouchers are created with ISACCEPTED=No — finance team must accept them in Tally before they appear in reports. Masters are auto-created if missing. It is categorised as a Write tool in the Tally Prime MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tally Prime MCP Server MCP server in PolicyLayer and add a rule for push_voucher_draft: 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 Tally Prime MCP Server. Nothing to install.
push_voucher_draft 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 push_voucher_draft 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 push_voucher_draft. 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.
push_voucher_draft is provided by the Tally Prime MCP Server MCP server (qalalabs/tally-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →