AI agents call search_stored_procedures_by_content 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) |
searchText | string | Yes | Text or pattern to search for in procedure definitions |
caseSensitive | boolean | — | Case sensitive search (default: false) |
connectionName | string | — | Named connection to use (e.g., 'production', 'staging') |
connectionString | string | — | SQL Server connection string (uses default if not provided) |
includeDefinitions | boolean | — | Include full procedure definitions in results (default: false) |
Parameters from the server's own tool schema.
This tool retrieves and queries stored procedure source code to find matches against search criteria. It performs no data modification, deletion, or execution of procedures—only inspection and pattern matching of existing stored procedure definitions. The sibling tools (describe_table, describe_view, describe_trigger, analyze_*) confirm this server specializes in non-destructive schema exploration.
From the tool's definition Tool name 'search_stored_procedures_by_content' and description 'Search for stored procedures containing specific text or patterns in their SQL definition' indicate read-only schema exploration.
Attacks that exploit this kind of access
Search for stored procedures containing specific text or patterns in their SQL definition. It is categorised as a Read tool in the Mssql MCP Server, which means it retrieves data without modifying state.
search_stored_procedures_by_content accepts 6 parameters: schema, searchText, caseSensitive, connectionName, connectionString, includeDefinitions. Required: searchText. 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 search_stored_procedures_by_content: 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.
search_stored_procedures_by_content 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 search_stored_procedures_by_content 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 search_stored_procedures_by_content. 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.
search_stored_procedures_by_content 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 →