AI agents call describe_view 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) |
viewName | string | Yes | Name of the view 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 view definition (default: true) |
Parameters from the server's own tool schema.
This tool retrieves and queries metadata about database views (definition, dependencies). It has no side effects — it does not execute code, modify data, delete objects, or trigger external operations. It fits the Read category profile: 'retrieves or queries data; no side effects (search, list, get, fetch)'.
From the tool's definition Tool name is 'describe_view' and description states it 'Get detailed information about a specific view including its definition and dependencies' — purely informational retrieval with no modification or execution of code.
Attacks that exploit this kind of access
Get detailed information about a specific view including its definition and dependencies. It is categorised as a Read tool in the Mssql MCP Server, which means it retrieves data without modifying state.
describe_view accepts 5 parameters: schema, viewName, connectionName, connectionString, includeDefinition. Required: viewName. 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_view: 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_view 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_view 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_view. 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_view 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 →