communications_get_subscription_status
Get subscription status for multiple contacts
This record as markdown: /tools/blacksand-software-hubspot-mcp/communications-get-subscription-status.md
What communications_get_subscription_status does on HubSpot MCP
AI agents call communications_get_subscription_status 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 communications_get_subscription_status is rated Low
This tool retrieves subscription status information for contacts without modifying any data. It is a straightforward read operation querying existing CRM data. While it accesses personal preference data (subscription status), the read-only nature and lack of side effects places it in the Read category with low severity.
From the tool's definition Tool name is 'communications_get_subscription_status' with description 'Get subscription status for multiple contacts'. The verb 'Get' and action of retrieving subscription status indicates a read-only query operation with no data modification.
Attacks that exploit this kind of access
The rule that runs communications_get_subscription_status 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 communications_get_subscription_status, this is the rule to start with:
communications_get_subscription_status 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 communications_get_subscription_status call is checked against it from then on.
Questions about communications_get_subscription_status
Get subscription status for multiple contacts. 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 communications_get_subscription_status: 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.
communications_get_subscription_status 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 communications_get_subscription_status 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 communications_get_subscription_status. 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.
communications_get_subscription_status 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