Get detailed structure of a table or view, including columns, types, constraints, and comments. Args: - table (string): Table or view name - schema (string, optional): Schema name, defaults to DB_SCHEMA env or 'public' Returns: Table structure with column names, data types, nullable, defaults, an...
AI agents call kb_describe_table 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 or view name to describe |
schema | string | — | Schema name (default: from DB_SCHEMA env or 'public') |
Parameters from the server's own tool schema.
This tool performs pure schema introspection—querying database metadata to understand table structure. It has no side effects, does not execute code, and cannot create, modify, or delete data. The 'describe' operation is a standard read-only database inspection pattern. No write, execute, or destructive operations are possible with this tool.
From the tool's definition Tool description states it retrieves 'detailed structure of a table or view, including columns, types, constraints, and comments.' Arguments are table/schema names for lookup only. Return value is structural metadata with no modification capability.
Attacks that exploit this kind of access
Get detailed structure of a table or view, including columns, types, constraints, and comments. Args: - table (string): Table or view name - schema (string, optional): Schema name, defaults to DB_SCHEMA env or 'public' Returns: Table structure with column names, data types, nullable, defaults, and comments. It is categorised as a Read tool in the Kingbase MCP Server, which means it retrieves data without modifying state.
kb_describe_table 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_describe_table: 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_describe_table 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_describe_table 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_describe_table. 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_describe_table 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 →