AI agents call hs_get_email_campaign_stats to retrieve information from Hubspot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns aggregated performance metrics from a marketing email campaign. It does not modify, delete, execute, or trigger any external operations. The blast radius of misuse is minimal—an agent could potentially view campaign performance data it shouldn't access, but cannot alter records, run processes, or move money. Classified as Read with low severity.
From the tool's definition Tool retrieves performance statistics (opens, clicks, bounces, unsubscribes) for a specific marketing email. The verb 'Get' and the nature of the requested data (read-only metrics) confirm this is a read operation with no side effects.
Attacks that exploit this kind of access
Get performance statistics (opens, clicks, bounces, unsubscribes) for a specific marketing email. It is categorised as a Read tool in the Hubspot MCP Server, which means it retrieves data without modifying state.
Register the Hubspot MCP server in PolicyLayer and add a rule for hs_get_email_campaign_stats: 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. Nothing to install.
hs_get_email_campaign_stats 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 hs_get_email_campaign_stats 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 hs_get_email_campaign_stats. 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.
hs_get_email_campaign_stats is provided by the Hubspot MCP server (zleventer/hubspot-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 →