Get the current Sitecore user.
AI agents call security-get-current-user 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 performs a read-only operation to retrieve the identity of the authenticated user in the Sitecore system. It has no side effects, does not execute code, does not modify data, and does not delete or move resources. The blast radius of misuse is minimal—an agent could learn who the current user is, which is typically low-risk metadata. This is a standard authentication/identity lookup function.
From the tool's definition Tool name 'security-get-current-user' and description 'Get the current Sitecore user' indicate a query operation that retrieves user identity information without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
Get the current Sitecore user. 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-current-user: 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-current-user 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-current-user 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-current-user. 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-current-user 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 →