Get storage and usage statistics for a table, including row count, size, and dead tuples. Args: - table (string): Table name - schema (string, optional): Schema name, defaults to DB_SCHEMA env or 'public' Returns: Table size, row count, index size, dead tuples, and last vacuum/analyze times.
AI agents call kb_table_stats to retrieve information from Kingbase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
table | string | Yes | Table name to get statistics for |
schema | string | — | Schema name (default: from DB_SCHEMA env or 'public') |
Parameters from the server's own tool schema.
This tool performs a pure query operation to fetch table metadata and statistics. It has no side effects, does not modify data, does not execute arbitrary code, and does not delete or move resources. It is analogous to inspecting system catalogs (e.g., pg_stat_user_tables in PostgreSQL). Low severity because misuse yields only information disclosure with no destructive or operational impact.
From the tool's definition Tool retrieves statistics ('Get storage and usage statistics for a table, including row count, size, and dead tuples') without modifying data. Returns read-only metadata: 'Table size, row count, index size, dead tuples, and last vacuum/analyze times.'
Attacks that exploit this kind of access
Get storage and usage statistics for a table, including row count, size, and dead tuples. Args: - table (string): Table name - schema (string, optional): Schema name, defaults to DB_SCHEMA env or 'public' Returns: Table size, row count, index size, dead tuples, and last vacuum/analyze times. It is categorised as a Read tool in the Kingbase MCP Server, which means it retrieves data without modifying state.
kb_table_stats accepts 2 parameters: table, schema. Required: table. The full parameter table on this page comes from the server's own tool schema.
Register the Kingbase MCP server in PolicyLayer and add a rule for kb_table_stats: 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 Kingbase. Nothing to install.
kb_table_stats 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 kb_table_stats 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 kb_table_stats. 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.
kb_table_stats is provided by the Kingbase MCP server (kingbase-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 →