hubspot_get_meeting
Get a specific meeting engagement by its ID.
This record as markdown: /tools/adeel0x01-hubspot-mcp-tools/hubspot-get-meeting.md
What hubspot_get_meeting does on HubSpot MCP Server
AI agents call hubspot_get_meeting 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_get_meeting is rated Low
This tool retrieves a single meeting record by ID from HubSpot's engagement system. It performs a read-only query operation with no capability to modify, delete, or execute external actions. The retrieval of CRM meeting data poses minimal risk even if misused by an AI agent, as it only exposes existing information without causing changes to the system.
From the tool's definition Tool name is 'hubspot_get_meeting' and description states 'Get a specific meeting engagement by its ID' — uses 'Get' verb and retrieves data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs hubspot_get_meeting 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_get_meeting, this is the rule to start with:
hubspot_get_meeting 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_get_meeting call is checked against it from then on.
Questions about hubspot_get_meeting
Get a specific meeting engagement by its ID. 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_get_meeting: 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_get_meeting 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_get_meeting 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_get_meeting. 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_get_meeting 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