hubspot_list_meetings
List meeting engagements in HubSpot with pagination.
This record as markdown: /tools/adeel0x01-hubspot-mcp-tools/hubspot-list-meetings.md
What hubspot_list_meetings does on HubSpot MCP Server
AI agents call hubspot_list_meetings to retrieve information from HubSpot MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why hubspot_list_meetings is rated Low
This tool retrieves and queries meeting engagement records from HubSpot without creating, modifying, deleting, or executing any operations. It has no side effects beyond data retrieval. Pagination is a standard read-operation feature.
From the tool's definition Tool name 'hubspot_list_meetings' and description 'List meeting engagements in HubSpot with pagination' indicate retrieval of existing meeting data with no modification or deletion capability. The 'list' action is a quintessential read operation.
Attacks that exploit this kind of access
The rule that runs hubspot_list_meetings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and HubSpot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hubspot_list_meetings, this is the rule to start with:
hubspot_list_meetings 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 Server, apply this rule, and every hubspot_list_meetings call is checked against it from then on.
Questions about hubspot_list_meetings
List meeting engagements in HubSpot with pagination. It is categorised as a Read tool in the HubSpot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the HubSpot MCP Server MCP server in PolicyLayer and add a rule for hubspot_list_meetings: 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 Server. Nothing to install.
hubspot_list_meetings 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 hubspot_list_meetings 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 hubspot_list_meetings. 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.
hubspot_list_meetings is provided by the HubSpot MCP Server MCP server (adeel0x01/hubspot-mcp-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on HubSpot MCP Server, and thousands of servers like it.
This server
Across the catalogue