AI agents call find_lookup_tables 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) |
maxRows | number | — | Maximum rows to consider as lookup table (default: 1000) |
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 performs schema discovery—querying metadata to classify tables by their structural patterns. It retrieves and analyzes information about existing tables without creating, modifying, deleting, or executing code. This is a pure read operation with negligible risk even if misused by an agent, as it only exposes table metadata already accessible via schema queries.
From the tool's definition Tool name and description indicate identification/discovery of existing tables ('Identify reference/lookup tables automatically based on table patterns'). No modification, deletion, or execution of arbitrary operations occurs.
Attacks that exploit this kind of access
Identify reference/lookup tables automatically based on table patterns. It is categorised as a Read tool in the Mssql MCP Server, which means it retrieves data without modifying state.
find_lookup_tables accepts 4 parameters: schema, maxRows, 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_lookup_tables: 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_lookup_tables 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_lookup_tables 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_lookup_tables. 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_lookup_tables 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 →