AI agents call find_computed_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) |
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 queries and retrieves metadata about computed columns and their formulas from the database schema. It performs no modifications, deletions, or code execution—purely informational access to understand how computed columns are derived. The sibling tools (analyze_*, describe_*) all follow a Read pattern. Confidence is high because the description is explicit about the read-only nature of the operation.
From the tool's definition Tool description states 'List computed columns and their formulas' which is a retrieval operation with no side effects. The verb 'List' and context of 'understanding' business logic indicate data inspection only.
Attacks that exploit this kind of access
List computed columns and their formulas to understand derived business logic. It is categorised as a Read tool in the Mssql MCP Server, which means it retrieves data without modifying state.
find_computed_columns 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 find_computed_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.
find_computed_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 find_computed_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 find_computed_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.
find_computed_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 →