Get details and recent vouchers for a specific ledger.
AI agents call get_ledger 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.
This tool retrieves and queries ledger information and historical voucher records. It performs no create, modify, delete, or execute operations. The action is purely informational, consistent with a Read category tool. The low severity reflects minimal blast radius—misuse would expose accounting data but not alter financial records or commit obligations.
From the tool's definition Tool name 'get_ledger' and description 'Get details and recent vouchers for a specific ledger' indicate retrieval of data without modification or side effects.
Attacks that exploit this kind of access
Get details and recent vouchers for a specific ledger. 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_ledger: 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_ledger 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_ledger 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_ledger. 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_ledger 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 →