Paginated list of base tables. Use offset/limit to walk the catalog. Returns total row count for the caller to size pagination.
AI agents call list_tables to retrieve information from Mssql Mcp Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
dbKey | string | — | Database key (lowercased). Optional in single-database mode. Call `list_databases` to discover valid keys. |
limit | integer | — | Max rows to return (1..1000). |
offset | integer | — | Row offset for pagination. |
Parameters from the server's own tool schema.
This tool only queries and lists table metadata from the database schema. It has no side effects, cannot modify data, and cannot execute operations. It is a straightforward Read operation that retrieves structural information about the database. The low severity reflects minimal blast radius even if misused - an attacker can only discover table names and structure, not access sensitive data or modify anything.
From the tool's definition Tool returns a 'Paginated list of base tables' with 'offset/limit' pagination and 'total row count' - purely informational catalog operations with no data modification or execution capability.
Attacks that exploit this kind of access
Paginated list of base tables. Use offset/limit to walk the catalog. Returns total row count for the caller to size pagination. It is categorised as a Read tool in the Mssql Mcp Node MCP Server, which means it retrieves data without modifying state.
list_tables accepts 3 parameters: dbKey, limit, offset. The full parameter table on this page comes from the server's own tool schema.
Register the Mssql Mcp Node MCP server in PolicyLayer and add a rule for list_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 Mcp Node. Nothing to install.
list_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 list_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 list_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.
list_tables is provided by the Mssql Mcp Node MCP server (mssql-mcp-node). 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 →