Update an existing SCIM resource (PUT)
AI agents use updateResource to create or update resources in SCIM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SCIM MCP Server environment.
This tool creates or modifies data reversibly through a PUT operation on SCIM resources. It does not delete data (which would be Destructive) nor execute arbitrary code (Execute). However, it can modify critical identity/access management data (SCIM manages users, groups, and entitlements), so unauthorized updates could have significant impact on system access and configuration.
From the tool's definition Tool description states 'Update an existing SCIM resource (PUT)'. PUT is an HTTP method that modifies existing data. The sibling tools include deleteResource and createResource, confirming this server manages SCIM resource lifecycle operations.
Attacks that exploit this kind of access
Update an existing SCIM resource (PUT). It is categorised as a Write tool in the SCIM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SCIM MCP Server MCP server in PolicyLayer and add a rule for updateResource: 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 SCIM MCP Server. Nothing to install.
updateResource 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 updateResource 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 updateResource. 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.
updateResource is provided by the SCIM MCP Server MCP server (limosa-io/mcp-scim). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
updateResource is one line of SCIM MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →