Tests if a Sitecore user exists and has specific properties.
AI agents call security-test-account 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 information about user accounts and their properties without creating, modifying, or deleting data. It is a read-only query operation. Severity is low because user existence/property checks pose minimal risk even if misused by an agent, as no data is altered and the information returned is security-related metadata that could be gathered through other means.
From the tool's definition Tool description states it 'Tests if a Sitecore user exists and has specific properties' - this is a query/check operation with no modification or side effects. The verb 'tests' combined with 'has' indicates reading user existence and attributes.
Attacks that exploit this kind of access
Tests if a Sitecore user exists and has specific properties. 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-test-account: 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-test-account 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-test-account 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-test-account. 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-test-account 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 →