AI agents call analyze_check_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) |
tableName | string | — | Filter by specific table name |
connectionName | string | — | Named connection to use (e.g., 'production', 'staging') |
connectionString | string | — | SQL Server connection string (uses default if not provided) |
Parameters from the server's own tool schema.
This tool retrieves and examines check constraint metadata from the database schema. It performs no writes, deletes, code execution, or financial operations. The blast radius is minimal—misuse would only expose database schema information that the AI already has query access to. It falls squarely in the Read category alongside sibling tools like describe_table and describe_view.
From the tool's definition Tool name 'analyze_check_constraints' and description 'Extract and analyze business rules from check constraints' indicate data retrieval and inspection of database metadata.
Attacks that exploit this kind of access
Extract and analyze business rules from check constraints. It is categorised as a Read tool in the Mssql MCP Server, which means it retrieves data without modifying state.
analyze_check_constraints accepts 4 parameters: schema, tableName, connectionName, 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 analyze_check_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.
analyze_check_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 analyze_check_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 analyze_check_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.
analyze_check_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 →