AI agents call describe_trigger 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 |
|---|---|---|---|
triggerName | string | Yes | Name of the trigger to describe |
connectionName | string | — | Named connection to use (e.g., 'production', 'staging') |
connectionString | string | — | SQL Server connection string (uses default if not provided) |
includeDefinition | boolean | — | Include the trigger definition (default: true) |
Parameters from the server's own tool schema.
This tool retrieves and queries trigger definitions and metadata from the database schema. It has no side effects—it does not execute the trigger, modify data, or change database structure. It is purely informational, similar to sibling tools like 'describe_stored_procedure' and 'describe_table' which are all Read category tools for schema exploration.
From the tool's definition Tool name 'describe_trigger' and description 'Get detailed information about a specific trigger including its definition and events' indicate retrieval of metadata and trigger source code without modification.
Attacks that exploit this kind of access
Get detailed information about a specific trigger including its definition and events. It is categorised as a Read tool in the Mssql MCP Server, which means it retrieves data without modifying state.
describe_trigger accepts 4 parameters: triggerName, connectionName, connectionString, includeDefinition. Required: triggerName. 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 describe_trigger: 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.
describe_trigger 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 describe_trigger 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 describe_trigger. 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.
describe_trigger 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 →