Get contacts from a specific mailing list.
AI agents call get_contacts to retrieve information from XEM Email MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves contact data from an existing mailing list without creating, modifying, deleting, or executing any operations. It is a straightforward read operation on stored contact information. The severity is low because contact list retrieval, while potentially exposing personal data, is a standard query operation without destructive or financial impact.
From the tool's definition Tool name is 'get_contacts' and description states 'Get contacts from a specific mailing list.' This is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get contacts from a specific mailing list. It is categorised as a Read tool in the XEM Email MCP Server MCP Server, which means it retrieves data without modifying state.
Register the XEM Email MCP Server MCP server in PolicyLayer and add a rule for get_contacts: 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 XEM Email MCP Server. Nothing to install.
get_contacts 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_contacts 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_contacts. 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_contacts is provided by the XEM Email MCP Server MCP server (mailxem/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 →