get_vouchers
AI agents call get_vouchers to retrieve information from TallyPrime MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on naming convention and parallel tools, get_vouchers most likely retrieves or lists existing voucher data without modifying state. The absence of a description lowers confidence slightly, but the 'get_' prefix and accounting context strongly suggest a read-only query operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_vouchers' indicates a retrieval operation; no description provided. Sibling tools named 'create_*' are Write/Financial, while 'get_*' tools (get_active_company, get_all_groups, get_all_ledgers) are consistently Read operations on this server.
Attacks that exploit this kind of access
get_vouchers. It is categorised as a Read tool in the TallyPrime MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TallyPrime MCP Server MCP server in PolicyLayer and add a rule for get_vouchers: 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.
get_vouchers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_vouchers 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 get_vouchers. 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.
get_vouchers 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 →