Get the Stock Summary (inventory) from TallyPrime as of a date.
AI agents call get_stock_summary to retrieve information from TallyPrime MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves stock/inventory information from TallyPrime accounting software. The verb 'Get' and the absence of any modification language ('create', 'update', 'delete') clearly indicate a read-only operation. There are no side effects, no data is created or destroyed, and no financial transactions are initiated.
From the tool's definition Tool name 'get_stock_summary' and description 'Get the Stock Summary (inventory) from TallyPrime as of a date' indicate a read-only query operation that retrieves inventory data without modifying state.
Attacks that exploit this kind of access
Get the Stock Summary (inventory) from TallyPrime as of a date. It is categorised as a Read tool in the TallyPrime MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TallyPrime MCP Server MCP server in PolicyLayer and add a rule for get_stock_summary: 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 TallyPrime MCP Server. Nothing to install.
get_stock_summary 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 get_stock_summary 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 get_stock_summary. 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.
get_stock_summary is provided by the TallyPrime MCP Server MCP server (svharivinod/tallyprime-mcp). 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 →