Create multiple notes in a single request
AI agents use notes_batch_create to create or update resources in HubSpot MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HubSpot MCP Server environment.
This tool creates (writes) notes in HubSpot's CRM system, modifying the database reversibly. Batch creation allows multiple writes in one call, increasing blast radius if misused (e.g., spam creation, unauthorized note injection), warranting medium severity. It does not delete, execute code, or commit financial transactions.
From the tool's definition Tool name 'notes_batch_create' and description 'Create multiple notes in a single request' indicate data creation operations. The batch capability amplifies the write scope.
Attacks that exploit this kind of access
Create multiple notes in a single request. It is categorised as a Write tool in the HubSpot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the HubSpot MCP Server MCP server in PolicyLayer and add a rule for notes_batch_create: 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.
notes_batch_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the notes_batch_create 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 notes_batch_create. 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.
notes_batch_create is provided by the HubSpot MCP Server MCP server (kozo93/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 →