AI agents call list_constraints to retrieve information from Mssql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
schema | string | — | Schema name (default: dbo) |
connectionName | string | — | Named connection to use (e.g., 'production', 'staging') |
constraintType | string | — | Filter by constraint type (default: ALL) |
connectionString | string | — | SQL Server connection string (uses default if not provided) |
Parameters from the server's own tool schema.
This tool queries and retrieves metadata about database constraints without creating, modifying, deleting, or executing any operations. It is purely informational schema exploration, consistent with sibling tools like describe_table, describe_view, and analyze_* tools that also perform read-only analysis.
From the tool's definition Tool name 'list_constraints' and description 'List all constraints...across tables in the database' indicate a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
List all constraints (check, unique, foreign key, etc.) across tables in the database. It is categorised as a Read tool in the Mssql MCP Server, which means it retrieves data without modifying state.
list_constraints accepts 4 parameters: schema, connectionName, constraintType, connectionString. The full parameter table on this page comes from the server's own tool schema.
Register the Mssql MCP server in PolicyLayer and add a rule for 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 Mssql. Nothing to install.
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 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 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.
list_constraints is provided by the Mssql MCP server (mssql-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 →