List all constraints (PK, FK, UNIQUE, CHECK) on a table. Args: - table (string): Table name - schema (string, optional): Schema name, defaults to DB_SCHEMA env or 'public' Returns: List of constraints with name, type, columns, and referenced table (for FK).
AI agents call kb_list_constraints 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 list constraints for |
schema | string | — | Schema name (default: from DB_SCHEMA env or 'public') |
Parameters from the server's own tool schema.
This tool queries and retrieves schema metadata about table constraints (PK, FK, UNIQUE, CHECK). It performs no side effects, creates no data, executes no operations, and modifies nothing. It is a pure read/inspection operation on database schema information, analogous to querying system catalogs. Misuse carries minimal risk since an AI agent cannot damage data or systems by merely listing constraints.
From the tool's definition Tool name 'kb_list_constraints' and description state it 'List all constraints' with no modification, deletion, or execution capabilities. Returns constraint metadata only.
Attacks that exploit this kind of access
List all constraints (PK, FK, UNIQUE, CHECK) on a table. Args: - table (string): Table name - schema (string, optional): Schema name, defaults to DB_SCHEMA env or 'public' Returns: List of constraints with name, type, columns, and referenced table (for FK). It is categorised as a Read tool in the Kingbase MCP Server, which means it retrieves data without modifying state.
kb_list_constraints 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_list_constraints: 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_list_constraints 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_list_constraints 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_list_constraints. 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_list_constraints 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 →