AI agents call hubspot_owners to retrieve information from Access without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves organizational user information from HubSpot without creating, modifying, deleting, or executing any actions. It is purely informational and serves as a lookup utility. The low severity reflects that while the data could include email addresses, this is typically already semi-public organizational information, and the blast radius of accidental misuse is minimal.
From the tool's definition Tool description states 'List all HubSpot owners' — a retrieval operation with no modification or side effects. Returns read-only data (IDs, names, email addresses).
Attacks that exploit this kind of access
List all HubSpot owners (team members) with their IDs, names, and email addresses. Use this to get owner IDs needed by hubspot_create_note and hubspot_log_call. It is categorised as a Read tool in the Access MCP Server, which means it retrieves data without modifying state.
Register the Access MCP server in PolicyLayer and add a rule for hubspot_owners: 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 Access. Nothing to install.
hubspot_owners 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_owners 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_owners. 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_owners is provided by the Access MCP server (scottpedia0/access). 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 →