fetches GL stock item account statement with voucher level details containing fields date, voucher_type, voucher_number, party_name, quantity, amount, narration, tracking_number, voucher_category. party_name = ledger_name. quantity = inward as positive and outward as negative. amount = debit is n...
AI agents call stock-item-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 retrieves read-only financial/inventory data from Tally Prime ERP including transaction history, quantities, and amounts. No data is created, modified, or deleted. Medium severity because it exposes detailed financial transaction data including party names, amounts, and voucher details which could be sensitive.
From the tool's definition fetches GL stock item account statement with voucher level details
Documented attack patterns abuse exactly the kind of access stock-item-account gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tally Prime MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for stock-item-account:
{
"version": "1",
"default": "deny",
"tools": {
"stock-item-account": {}
}
}stock-item-account is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
fetches GL stock item account statement with voucher level details containing fields date, voucher_type, voucher_number, party_name, quantity, amount, narration, tracking_number, voucher_category. party_name = ledger_name. quantity = inward as positive and outward as negative. amount = debit is negative and credit is positive, narration = notes / remarks. for calculating closing balance of quantity, consider rows with tracking_number as empty as it is, but for rows with tracking_number having text value, then duplicate rows need to be removed by preparing intermediate output with aggregation of tracking_number and voucher_category with sum of quantity and then comparing quantity of Receipt Note with Purchase and Delivery Note with Sales to identify and remove the rows with Receipt Note and Delivery Note if they are found to be tracked fully / partially . 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 stock-item-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.
stock-item-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 stock-item-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 stock-item-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.
stock-item-account is provided by the Tally Prime MCP Server MCP server (dhananjay1405/tally-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tally Prime MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
19 Tally Prime MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.