hubspot_log_call · Access MCP: Risk & Policy

WHAT IT DOES

What hubspot_log_call does on Access

AI agents use hubspot_log_call to create or update resources in Access — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Access environment.

WHY IT NEEDS A POLICY

Why hubspot_log_call needs a policy

This tool creates a new call engagement record on a HubSpot contact, which is a reversible write operation (the record can be deleted later). It modifies CRM data by adding a call log, but does not delete, execute code, or involve financial transactions. Misuse could pollute CRM records with false call logs, affecting sales/support workflows.

From the tool's definition 'Log a completed phone call as an engagement on a HubSpot contact. Side effect: the call record appears on the contact'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hubspot_log_call Rate-limited

hubspot_log_call stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hubspot_log_call": {
      "limits": [
        {
          "counter": "hubspot_log_call_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Access, so you can run agents against it safely.

FAQ

Questions about hubspot_log_call

What does the hubspot_log_call tool do? +

Log a completed phone call as an engagement on a HubSpot contact. Side effect: the call record appears on the contact. It is categorised as a Write tool in the Access MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on hubspot_log_call? +

Register the Access MCP server in PolicyLayer and add a rule for hubspot_log_call: 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.

What risk level is hubspot_log_call? +

hubspot_log_call is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit hubspot_log_call? +

Yes. Add a rate_limit block to the hubspot_log_call 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.

How do I block hubspot_log_call completely? +

Set action: deny in the PolicyLayer policy for hubspot_log_call. 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.

What MCP server provides hubspot_log_call? +

hubspot_log_call 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.