Retrieve SCIM schema information
AI agents call schemas 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.
The schemas tool retrieves (queries) schema metadata from a SCIM 2.0 API endpoint. This is a non-destructive, informational operation with no side effects. It does not create, modify, delete resources, execute code, or commit financial transactions. It falls squarely under the Read category with low severity since schema information is typically non-sensitive metadata used for understanding API structure.
From the tool's definition Tool description states 'Retrieve SCIM schema information' — a read-only operation that queries metadata without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Retrieve SCIM schema information. 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 schemas: 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.
schemas 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 schemas 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 schemas. 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.
schemas 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 →