List CRM objects of a specific type with optional filtering and pagination
AI agents call crm_list_objects 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.
This tool retrieves and queries CRM data without side effects. The verb 'list' combined with 'filtering and pagination' describes a standard read operation that returns existing data. No creation, modification, deletion, or execution of code is mentioned. While the data retrieved could be sensitive (CRM information), the tool itself poses minimal risk as it merely queries and returns information.
From the tool's definition Tool name 'crm_list_objects' and description 'List CRM objects of a specific type with optional filtering and pagination' indicate data retrieval with no modification capability.
Documented attack patterns abuse exactly the kind of access crm_list_objects 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 crm_list_objects:
{
"version": "1",
"default": "deny",
"tools": {
"crm_list_objects": {}
}
}crm_list_objects 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.
List CRM objects of a specific type with optional filtering and pagination. 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 crm_list_objects: 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.
crm_list_objects 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 crm_list_objects 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 crm_list_objects. 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.
crm_list_objects 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.