hubspot.objects.pull
AI agents call hubspot.objects.pull to retrieve information from G Gremlin Hubspot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The naming convention ('pull') and position within a suite of tools where query and extraction operations are documented suggests this retrieves data from HubSpot without modification. However, the empty description and 'unlimited' extraction capability warrants medium severity due to potential for excessive data access or exposure of sensitive CRM information.
From the tool's definition Tool name 'pull' combined with sibling tools context (hubspot.objects.query, hubspot.engagements.pull) indicates data retrieval. Server description mentions 'unlimited record extraction' which aligns with a Read operation.
Attacks that exploit this kind of access
hubspot.objects.pull. It is categorised as a Read tool in the G Gremlin Hubspot MCP Server, which means it retrieves data without modifying state.
Register the G Gremlin Hubspot MCP server in PolicyLayer and add a rule for hubspot.objects.pull: 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 G Gremlin Hubspot. Nothing to install.
hubspot.objects.pull 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.objects.pull 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.objects.pull. 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.objects.pull is provided by the G Gremlin Hubspot MCP server (mikeheilmann1024/g-gremlin-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 →