emails_search
Search emails with specific filters
This record as markdown: /tools/blacksand-software-hubspot-mcp/emails-search.md
What emails_search does on HubSpot MCP
AI agents call emails_search to retrieve information from HubSpot MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why emails_search is rated Low
The search functionality is a read-only operation that queries existing email data using filters. It does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an agent could retrieve email data it shouldn't access, but cannot alter or destroy information. This is a standard retrieval pattern consistent with the 'Read' category.
From the tool's definition Tool name 'emails_search' and description 'Search emails with specific filters' indicate a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs emails_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and HubSpot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For emails_search, this is the rule to start with:
emails_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect HubSpot MCP, apply this rule, and every emails_search call is checked against it from then on.
Questions about emails_search
Search emails with specific filters. It is categorised as a Read tool in the HubSpot MCP MCP Server, which means it retrieves data without modifying state.
Register the HubSpot MCP server in PolicyLayer and add a rule for emails_search: 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 HubSpot MCP. Nothing to install.
emails_search 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 emails_search 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 emails_search. 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.
emails_search is provided by the HubSpot MCP server (blacksand-software/hubspot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on HubSpot, and thousands of servers like it.
This server
Across the catalogue