Retrieve SCIM service provider configuration including supported features, authentication schemes, and protocol capabilities
AI agents call serviceProviderConfig to retrieve information from SCIM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration metadata from a SCIM service provider. The verb 'Retrieve' and the nature of the data (configuration, capabilities, authentication schemes) indicate a non-destructive read operation with no side effects. No data is created, modified, deleted, or financial operations are involved.
From the tool's definition Tool name 'serviceProviderConfig' and description 'Retrieve SCIM service provider configuration' indicate a read-only query operation that fetches metadata about supported features, authentication schemes, and protocol capabilities without modifying any data.
Attacks that exploit this kind of access
Retrieve SCIM service provider configuration including supported features, authentication schemes, and protocol capabilities. It is categorised as a Read tool in the SCIM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SCIM MCP Server MCP server in PolicyLayer and add a rule for serviceProviderConfig: 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.
serviceProviderConfig is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the serviceProviderConfig 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 serviceProviderConfig. 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.
serviceProviderConfig 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.
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 →