gst-voucher-details

fetches GST tax breakup of vouchers (Sales, Purchase, Debit Note, Credit Note) for a date range with fields date, voucher_type, voucher_number, party_name, party_gstin, place_of_supply, taxable_value, cgst_rate, cgst_amount, sgst_rate, sgst_amount, igst_rate, igst_amount, cess_amount, invoice_val...

Server Tally Prime MCP Server jina-code-systems/tally-mcp-server
Category Read
Risk class Low
Parameters 00 required

What gst-voucher-details does on Tally Prime MCP Server

AI agents call gst-voucher-details 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.

Why gst-voucher-details needs a policy

The tool retrieves and returns GST voucher data for a specified date range with no side effects. It caches results in an in-memory DuckDB table for further querying, but does not create, modify, or delete any data. This is a pure read/query operation.

From the tool's definition fetches GST tax breakup of vouchers (Sales, Purchase, Debit Note, Credit Note) for a date range

Questions about gst-voucher-details

What does the gst-voucher-details tool do? +

fetches GST tax breakup of vouchers (Sales, Purchase, Debit Note, Credit Note) for a date range with fields date, voucher_type, voucher_number, party_name, party_gstin, place_of_supply, taxable_value, cgst_rate, cgst_amount, sgst_rate, sgst_amount, igst_rate, igst_amount, cess_amount, invoice_value, reverse_charge, narration. amounts negative = debit, positive = credit. 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.

How do I enforce a policy on gst-voucher-details? +

Register the Tally Prime MCP Server MCP server in PolicyLayer and add a rule for gst-voucher-details: 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.

What risk level is gst-voucher-details? +

gst-voucher-details is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit gst-voucher-details? +

Yes. Add a rate_limit block to the gst-voucher-details 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.

How do I block gst-voucher-details completely? +

Set action: deny in the PolicyLayer policy for gst-voucher-details. 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.

What MCP server provides gst-voucher-details? +

gst-voucher-details 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.