AI agents call meetings_search to retrieve information from HubSpot MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations are read-only and retrieve data without side effects. Searching meetings in a CRM context retrieves existing records for filtering and discovery purposes only. The sibling tools show a pattern of CRUD operations where search/list/get are distinct from create/update/delete, confirming this as a Read category tool.
From the tool's definition Tool name 'meetings_search' and description 'Search meetings with specific filters' indicate a query/search operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access meetings_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HubSpot MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for meetings_search:
{
"version": "1",
"default": "deny",
"tools": {
"meetings_search": {}
}
}meetings_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search meetings with specific filters. 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 meetings_search: 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.
meetings_search 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 meetings_search 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 meetings_search. 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.
meetings_search is provided by the HubSpot MCP server (shinzo-labs/hubspot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 112 HubSpot MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
112 HubSpot MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.