Get a Sitecore users by filter.
AI agents call security-get-user-by-filter to retrieve information from SitecoreMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user information from Sitecore based on filter criteria. It performs a read-only query operation with no side effects, no data creation, modification, or deletion. The verb 'get' and the retrieval-focused description confirm this is a Read operation.
From the tool's definition Tool name contains 'get' and description states 'Get a Sitecore users by filter' — both indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
Get a Sitecore users by filter. It is categorised as a Read tool in the SitecoreMCP MCP Server, which means it retrieves data without modifying state.
Register the Sitecore MCP server in PolicyLayer and add a rule for security-get-user-by-filter: 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.
security-get-user-by-filter 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 security-get-user-by-filter 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 security-get-user-by-filter. 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.
security-get-user-by-filter 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 →