AI agents call security-get-role-by-filter to retrieve information from Mcp Sitecore without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves Sitecore role information based on filter parameters. It performs a read-only operation with no side effects, data modification, or destructive actions. The blast radius of misuse is low since it only exposes existing role metadata that an attacker with access to this MCP server could likely enumerate through other means.
From the tool's definition Tool name contains 'get' and description states 'Get Sitecore roles by filter criteria' — retrieves role data without modification.
Documented attack patterns abuse exactly the kind of access security-get-role-by-filter gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Sitecore, and nothing reaches the server without passing your rules. This is the rule we recommend for security-get-role-by-filter:
{
"version": "1",
"default": "deny",
"tools": {
"security-get-role-by-filter": {}
}
} security-get-role-by-filter is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get Sitecore roles by filter criteria. It is categorised as a Read tool in the Mcp Sitecore MCP Server, which means it retrieves data without modifying state.
Register the Mcp Sitecore MCP server in PolicyLayer and add a rule for security-get-role-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 Mcp Sitecore. Nothing to install.
security-get-role-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-role-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-role-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-role-by-filter is provided by the Mcp Sitecore MCP server (@antonytm/mcp-sitecore-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Sitecore, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
149 Mcp Sitecore tools catalogued and risk-classified — across an index of 43,000+ MCP servers.