Create a new view for a list or library with specified columns, row limit, and optional CAML filter.
AI agents use create_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.
The tool creates a new view (a reversible configuration change) on a SharePoint list or library. This is a Write operation: it modifies the schema/structure of SharePoint resources by adding a view, but the operation is reversible (the view can be deleted). It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition create_view" tool that "Create[s] a new view for a list or library" — this is a create operation that adds a new view configuration to SharePoint.
Attacks that exploit this kind of access
Create a new view for a list or library with specified columns, row limit, and optional CAML filter. 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 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 SharePoint 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 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 →