create_receipt_voucher
AI agents use create_receipt_voucher to create or update resources in TallyPrime MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TallyPrime MCP Server environment.
Receipt vouchers in accounting systems record incoming payments and are reversible transactions (can be deleted or amended). This is a Write operation that modifies the accounting ledger by creating a new record.
From the tool's definition Tool name is 'create_receipt_voucher' and server context shows it enables creation of accounting vouchers; sibling tools include 'create_journal_voucher', 'create_payment_voucher', 'create_purchase_voucher', and 'create_sales_voucher', all Write operations…
Attacks that exploit this kind of access
create_receipt_voucher. It is categorised as a Write tool in the TallyPrime MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TallyPrime MCP Server MCP server in PolicyLayer and add a rule for create_receipt_voucher: 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 TallyPrime MCP Server. Nothing to install.
create_receipt_voucher 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 create_receipt_voucher 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 create_receipt_voucher. 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.
create_receipt_voucher is provided by the TallyPrime MCP Server MCP server (svharivinod/tallyprime-mcp). 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 →