fetches profit and loss statement with fields like ledger_name, group_name, closing_balance. closing_balance negative is debit or expense and positive is credit or income. closing stock to be treated as credit, kindly fetch data from chart-of-accounts tool to pull group hierarchy before calling t...
AI agents call profit-loss 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/fetches financial report data (P&L statement) from Tally Prime ERP. It is read-only — it queries and returns data without creating, modifying, or deleting anything. The caching to an in-memory table is a transient side effect for downstream querying, not a persistent write.
From the tool's definition fetches profit and loss statement with fields like ledger_name, group_name, closing_balance... returns output cached in pglite postgres in-memory table
Documented attack patterns abuse exactly the kind of access profit-loss 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 profit-loss:
{
"version": "1",
"default": "deny",
"tools": {
"profit-loss": {}
}
}profit-loss 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 profit and loss statement with fields like ledger_name, group_name, closing_balance. closing_balance negative is debit or expense and positive is credit or income. closing stock to be treated as credit, kindly fetch data from chart-of-accounts tool to pull group hierarchy before calling this tool. for detailed ledger level analysis call trial-balance tool, 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 profit-loss: 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.
profit-loss 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 profit-loss 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 profit-loss. 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.
profit-loss 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.