AI agents use modify_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.
The tool modifies an existing database view, which is a reversible operation (the previous view definition can be restored). This is characteristic of Write operations. While it does not delete or irreversibly destroy data (Destructive), it also does not merely retrieve data (Read) or execute arbitrary code (Execute).
From the tool's definition Tool name 'modify_view' and description 'Modify an existing view' indicate the tool creates or modifies database objects reversibly.
Documented attack patterns abuse exactly the kind of access modify_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 modify_view:
{
"version": "1",
"default": "deny",
"tools": {
"modify_view": {
"limits": [
{
"counter": "modify_view_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}modify_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.
Modify an existing 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 modify_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.
modify_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 modify_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 modify_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.
modify_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.