fetches GL ledger account statement with voucher level details containing fields date, voucher_type, voucher_number, party_name, amount, narration, party_gstin, cgst_amount, sgst_amount, igst_amount. amount = debit is negative and credit is positive. party_name = ledger_name. GST tax amounts (cgs...
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 and returns financial ledger data (dates, voucher types, amounts, GST fields) into an in-memory read-only cache. No data is created, modified, deleted, or any financial transaction is initiated. It is purely a read/query operation.
From the tool's definition fetches GL ledger account statement with voucher level details... returns output cached in DuckDB in-memory table
Attacks that exploit this kind of access
fetches GL ledger account statement with voucher level details containing fields date, voucher_type, voucher_number, party_name, amount, narration, party_gstin, cgst_amount, sgst_amount, igst_amount. amount = debit is negative and credit is positive. party_name = ledger_name. GST tax amounts (cgst_amount, sgst_amount, igst_amount) are included per voucher entry where applicable. returns output cached in DuckDB 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 (jina-code-systems/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 →