Update fields of an existing list item by its numeric ID.
AI agents use update_item 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 modifies fields of existing list items in SharePoint, which is a write operation. While the change is applied to SharePoint data, updates are generally reversible (can be undone or corrected by subsequent updates), distinguishing this from destructive operations.
From the tool's definition Tool name 'update_item' and description 'Update fields of an existing list item' indicate modification of existing data. This is a reversible operation that changes data in place without deletion.
Attacks that exploit this kind of access
Update fields of an existing list item by its numeric ID. 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_item: 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_item 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_item 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_item. 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_item 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 →