This record as markdown: /tools/blacksand-software-hubspot-mcp/emails-get.md
What emails_get does on HubSpot MCP
AI agents call emails_get 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_get is rated Low
This tool retrieves email details from the HubSpot CRM system without altering, deleting, or executing any operations. It is a straightforward read operation that queries data. The blast radius of misuse is minimal—an attacker could retrieve email content but cannot modify systems, execute code, delete data, or trigger financial transactions. Low severity is appropriate for information disclosure in a CRM context.
From the tool's definition Tool name 'emails_get' and description 'Get details of a specific email' indicate retrieval of existing data with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs emails_get 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_get, this is the rule to start with:
emails_get 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_get call is checked against it from then on.
Questions about emails_get
Get details of a specific email. 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_get: 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_get 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_get 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_get. 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_get 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