Resets item fields, specified as either names, fields or template fields by path.
AI agents use common-reset-item-field-by-path to create or update resources in SitecoreMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SitecoreMCP environment.
Resetting item fields in Sitecore modifies the item's field values, which qualifies as a Write operation. While it changes data, Sitecore maintains version history making it potentially reversible, hence medium severity rather than Destructive.
From the tool's definition 'Resets item fields' - resetting fields modifies data by returning them to default/empty state, but this is typically reversible via version history in Sitecore
Attacks that exploit this kind of access
Resets item fields, specified as either names, fields or template fields by path. It is categorised as a Write tool in the SitecoreMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sitecore MCP server in PolicyLayer and add a rule for common-reset-item-field-by-path: 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 SitecoreMCP. Nothing to install.
common-reset-item-field-by-path 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 common-reset-item-field-by-path 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 common-reset-item-field-by-path. 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.
common-reset-item-field-by-path is provided by the Sitecore MCP server (ramseur/mcp-sitecore-server). 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 →