fetches GL ledger account statement with voucher level details containing fields guid, date, voucher_type, voucher_number, alternate_ledger, party_name, amount, narration . amount = debit is negative and credit is positive. alternate_ledger = if amount is credit then ledger by which it is debited...
AI agents call ledger-account to retrieve information from Tally Prime MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only retrieves/fetches general ledger account statement data with voucher details. It reads financial records and caches them for querying, but does not create, modify, delete, or move any data. The output is stored in an in-memory table for further read-only SQL analysis.
From the tool's definition fetches GL ledger account statement with voucher level details... returns output cached in pglite postgres in-memory table
Attacks that exploit this kind of access
fetches GL ledger account statement with voucher level details containing fields guid, date, voucher_type, voucher_number, alternate_ledger, party_name, amount, narration . amount = debit is negative and credit is positive. alternate_ledger = if amount is credit then ledger by which it is debited and vice-a-versa (in case of multiple ledgers first one is displayed). returns output cached in pglite postgres in-memory table (specified in tableID property). Use query-database tool to run SQL queries against that table for further analysis. It is categorised as a Read tool in the Tally Prime MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tally Prime MCP Server MCP server in PolicyLayer and add a rule for ledger-account: 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.
ledger-account 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 ledger-account 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 ledger-account. 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.
ledger-account 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 →