hubspot_get_properties
Get all available properties for a HubSpot object type. Use this to discover what fields can be used when creating, updating, or searching objects.
This record as markdown: /tools/adeel0x01-hubspot-mcp-tools/hubspot-get-properties.md
What hubspot_get_properties does on HubSpot MCP Server
AI agents call hubspot_get_properties 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_properties is rated Low
This tool performs a read-only query operation that retrieves schema/metadata information about HubSpot object properties. It has no side effects, does not modify data, and serves only to list available fields for reference. This is a classic Read category operation with minimal security risk—even if an AI agent calls it repeatedly, the only impact is API usage.
From the tool's definition Tool is named 'get_properties' and described as retrieving 'all available properties for a HubSpot object type' to 'discover what fields can be used'.
Attacks that exploit this kind of access
The rule that runs hubspot_get_properties 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_properties, this is the rule to start with:
hubspot_get_properties 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_properties call is checked against it from then on.
Questions about hubspot_get_properties
Get all available properties for a HubSpot object type. Use this to discover what fields can be used when creating, updating, or searching objects. 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_properties: 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_properties 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_properties 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_properties. 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_properties 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