AI agents call detect_audit_columns 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') |
connectionString | string | — | SQL Server connection string (uses default if not provided) |
Parameters from the server's own tool schema.
This tool retrieves and analyzes information about audit columns in the database schema. It performs pattern detection on metadata (created/modified dates, user tracking fields) without creating, modifying, or deleting any data. The action is purely informational—examining the database structure to identify audit trail patterns.
From the tool's definition Tool name 'detect_audit_columns' and description 'Identify common audit trail patterns' indicates querying/inspection of existing schema metadata. No modification, deletion, or execution of operations is implied.
Attacks that exploit this kind of access
Identify common audit trail patterns (created/modified dates, user tracking). It is categorised as a Read tool in the Mssql MCP Server, which means it retrieves data without modifying state.
detect_audit_columns accepts 3 parameters: schema, 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 detect_audit_columns: 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.
detect_audit_columns 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 detect_audit_columns 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 detect_audit_columns. 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.
detect_audit_columns 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 →