Update an existing view: change columns, CAML query, row limit, or make it the default.
AI agents use update_view to create or update resources in SharePoint MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SharePoint MCP Server environment.
This tool modifies view configuration within SharePoint but does not delete or destroy views. The changes are reversible—views can be updated again to restore prior state, and the underlying data in the list remains intact. This qualifies as Write rather than Destructive.
From the tool's definition Tool description states 'Update an existing view: change columns, CAML query, row limit, or make it the default.' The verb 'update' and the description of modifying view properties (columns, CAML query, row limit, default status) indicates reversible…
Attacks that exploit this kind of access
Update an existing view: change columns, CAML query, row limit, or make it the default. It is categorised as a Write tool in the SharePoint MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SharePoint MCP Server MCP server in PolicyLayer and add a rule for update_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 SharePoint MCP Server. Nothing to install.
update_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 update_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 update_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.
update_view is provided by the SharePoint MCP Server MCP server (lukassevcik/sharepoint-mcp). 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 →