create or update ledger master data in Tally Prime, returns success count of created and / or altered records
AI agents use ledger-create-update to create or update resources in Tally Prime MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tally Prime MCP Server environment.
This tool modifies ledger account master data in an ERP system, which is a write operation that creates or reversibly updates records. While it affects financial data, it does not move money or create financial obligations (which would be Financial category), and it is not destructive (permanent deletion).
From the tool's definition Tool description explicitly states 'create or update ledger master data in Tally Prime, returns success count of created and / or altered records'. The terms 'create or update' and 'altered records' confirm write operations on financial master data.
Documented attack patterns abuse exactly the kind of access ledger-create-update 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 ledger-create-update:
{
"version": "1",
"default": "deny",
"tools": {
"ledger-create-update": {
"limits": [
{
"counter": "ledger-create-update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} ledger-create-update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
create or update ledger master data in Tally Prime, returns success count of created and / or altered records. It is categorised as a Write tool in the Tally Prime MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tally Prime MCP Server MCP server in PolicyLayer and add a rule for ledger-create-update: 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-create-update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ledger-create-update 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-create-update. 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-create-update 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.