AI agents use create_view to create or update resources in MSSQL MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MSSQL MCP Server environment.
Creating a view is a Write operation—it persistently modifies database schema by adding a new queryable object, but remains reversible through deletion (see sibling 'delete_view' tool). It does not destroy data or execute arbitrary code. Severity is medium because schema modifications can affect dependent objects and system behavior, but the impact is typically scoped to the view itself and queries that rely on it.
From the tool's definition Tool name 'create_view' and description 'Create a new view' indicate creation of a database object. MSSQL context shows this is reversible database schema modification via standard DDL operations.
Documented attack patterns abuse exactly the kind of access create_view gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MSSQL MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_view:
{
"version": "1",
"default": "deny",
"tools": {
"create_view": {
"limits": [
{
"counter": "create_view_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_view stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new view. It is categorised as a Write tool in the MSSQL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MSSQL MCP Server MCP server in PolicyLayer and add a rule for create_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 MCP Server. Nothing to install.
create_view is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_view is provided by the MSSQL MCP Server MCP server (jensenloke/mcp-sqlserver-pro). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MSSQL MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 MSSQL MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.