Find a contact by email address (Sidemail API)
AI agents call find-contact to retrieve information from Sidemail MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches for and retrieves contact information based on an email address. It has no side effects—it does not create, modify, delete, or execute external operations. The action is a simple lookup/query, making it a Read category tool. Severity is low because contact lookup poses minimal risk even if misused; the worst case is discovering contact information that may already be known or inferred.
From the tool's definition Tool name 'find-contact' and description 'Find a contact by email address' indicate a query operation that retrieves contact data without modification. The verb 'find' is a read operation.
Attacks that exploit this kind of access
Find a contact by email address (Sidemail API). It is categorised as a Read tool in the Sidemail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sidemail MCP Server MCP server in PolicyLayer and add a rule for find-contact: 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 Sidemail MCP Server. Nothing to install.
find-contact 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 find-contact 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 find-contact. 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.
find-contact is provided by the Sidemail MCP Server MCP server (sidemail/sidemail-mcp-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 →