create_journal_voucher
AI agents use create_journal_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.
Creating a journal voucher in accounting software modifies ledgers and financial records reversibly (entries can be deleted/adjusted later), but impacts financial reporting and bookkeeping accuracy. This is Write rather than Financial because it creates transaction records themselves rather than moving money between accounts or executing payments.
From the tool's definition Tool name 'create_journal_voucher' and sibling tools like 'create_payment_voucher', 'create_purchase_voucher', 'create_receipt_voucher', 'create_sales_voucher' all indicate creation of financial transaction records.
Attacks that exploit this kind of access
create_journal_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_journal_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_journal_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_journal_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_journal_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_journal_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 →