Count the total number of rows in a table
AI agents call count_rows to retrieve information from Database 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 aggregation query (COUNT) on a table. It retrieves metadata about table size with no side effects, modifications, or destructive operations. It falls squarely within the Read category alongside sibling tools like list_tables, preview_table, and sample_distinct. Severity is low because miscounting rows has no operational impact.
From the tool's definition Tool name 'count_rows' and description 'Count the total number of rows in a table' indicate a query operation that retrieves aggregate information without modifying data.
Attacks that exploit this kind of access
Count the total number of rows in a table. It is categorised as a Read tool in the Database MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Database MCP Server MCP server in PolicyLayer and add a rule for count_rows: 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 Database MCP Server. Nothing to install.
count_rows 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 count_rows 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 count_rows. 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.
count_rows is provided by the Database MCP Server MCP server (zeaozhang/database-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 →