queries a Tally Prime collection with selected fields and optional context like target company and reporting period. result is cached in pglite postgres in-memory table and returned as tableID. Use query-database tool to run SQL queries against that table for further analysis
AI agents call query-collection 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.
This tool performs a read-only query operation against an ERP database collection. It retrieves financial data (ledger balances, reports, stock summaries based on sibling tools) and caches results for analysis, but does not create, modify, delete, or execute arbitrary operations. The actual SQL execution against cached data is delegated to a separate 'query-database' tool.
From the tool's definition Tool 'queries a Tally Prime collection with selected fields' and 'result is cached... and returned as tableID'.
Attacks that exploit this kind of access
queries a Tally Prime collection with selected fields and optional context like target company and reporting period. result is cached in pglite postgres in-memory table and returned as tableID. 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 query-collection: 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.
query-collection 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 query-collection 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 query-collection. 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.
query-collection is provided by the Tally Prime MCP Server MCP server (qalalabs/tally-mcp-server). 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 →