AI agents call hs_list_workflows 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 queries and returns information about existing workflows without creating, modifying, deleting, or executing any actions. It is a standard read operation that retrieves workflow metadata only. Severity is low because unauthorized access to workflow names and types poses minimal direct risk compared to tools that could modify workflows or execute them.
From the tool's definition Tool name and description: 'List all HubSpot automation workflows with name, type, and enabled status.' The verb 'list' and the read-only nature of retrieving workflow metadata (name, type, enabled status) indicate this is a retrieval operation with no side…
Attacks that exploit this kind of access
List all HubSpot automation workflows with name, type, and enabled status. 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_list_workflows: 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_list_workflows 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_list_workflows 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_list_workflows. 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_list_workflows 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 →