query-database · Tally Prime MCP Server MCP: Risk & Policy

WHAT IT DOES

What query-database does on Tally Prime MCP Server

AI agents invoke query-database to trigger actions in Tally Prime MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why query-database needs a policy

This tool executes arbitrary SQL queries against a DuckDB in-memory database. While the description states it queries 'cached Tally Prime report data' (suggesting read-only intent), the tool accepts arbitrary SQL which could include destructive statements (DROP, DELETE) or other unintended operations. The execution of arbitrary SQL on a financial ERP-linked database represents a high severity risk.

From the tool's definition 'executes sql query on DuckDB in-memory database' and 'run complex analytical queries to aggregate, filter, sort results'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

query-database Rate-limited

query-database stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "query-database": {
      "limits": [
        {
          "counter": "query-database_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tally Prime MCP Server, so you can run agents against it safely.

FAQ

Questions about query-database

What does the query-database tool do? +

executes sql query on DuckDB in-memory database for querying cached Tally Prime report data in table generated as output by other tools (in tableID property from tool output response). These tables are temporary and will be dropped after 15 minutes automatically. Use this tool to run complex analytical queries to aggregate, filter, sort results. Returns output in tab separated format. It is categorised as a Execute tool in the Tally Prime MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on query-database? +

Register the Tally Prime MCP Server MCP server in PolicyLayer and add a rule for query-database: 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 query-database? +

query-database is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit query-database? +

Yes. Add a rate_limit block to the query-database 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 query-database completely? +

Set action: deny in the PolicyLayer policy for query-database. 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 query-database? +

query-database 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.