AI agents call list_functions 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) |
functionType | string | — | Filter by function type (default: ALL) |
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 enumerates user-defined functions from the database schema. It performs no write, execute, destructive, or financial operations—only querying and displaying existing metadata. The blast radius of misuse is minimal; an attacker could only discover function names and metadata already present in the database, with no ability to modify, delete, or execute arbitrary code through this tool alone.
From the tool's definition The tool name 'list_functions' and description 'List all user-defined functions' indicate a retrieval operation that queries database metadata without modification.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all user-defined functions (scalar, table-valued, etc.). It is categorised as a Read tool in the Mssql MCP Server, which means it retrieves data without modifying state.
list_functions accepts 4 parameters: schema, functionType, 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 list_functions: 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.
list_functions 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_functions 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_functions. 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_functions 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 →