Get subscriber by email
AI agents call get_subscriber_by_email to retrieve information from Sitecore Send without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves subscriber information based on an email address. It performs a query/lookup operation that returns data without creating, modifying, deleting, or executing any actions. This is a straightforward read operation with minimal risk — the only concern is potential exposure of subscriber personal data if misused, but the tool itself is not destructive or operationally dangerous.
From the tool's definition Tool name is 'get_subscriber_by_email' and description states 'Get subscriber by email' — purely a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get subscriber by email. It is categorised as a Read tool in the Sitecore Send MCP Server, which means it retrieves data without modifying state.
Register the Sitecore Send MCP server in PolicyLayer and add a rule for get_subscriber_by_email: 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 Sitecore Send. Nothing to install.
get_subscriber_by_email 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 get_subscriber_by_email 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 get_subscriber_by_email. 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.
get_subscriber_by_email is provided by the Sitecore Send MCP server (izharikov/send-mcp). 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 →