This record as markdown: /tools/io-github-portel-dev-ncp/create-contact.md
What create_contact does on Ncp
AI agents use create_contact to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why create_contact is rated Medium
This tool creates a new contact record in HubSpot, which is a reversible write operation. It modifies data by adding a new entry but does not delete, execute arbitrary code, or move money. The severity is medium because creating unauthorized contacts could lead to data pollution, privacy violations, or misuse of a CRM system, but the operation itself is non-destructive and can be remediated by deletion.
From the tool's definition Tool name 'create_contact' with description 'Create HubSpot contact' indicates creation of a new data record in an external CRM system (HubSpot).
Attacks that exploit this kind of access
The rule that runs create_contact safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_contact, this is the rule to start with:
create_contact 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every create_contact call is checked against it from then on.
Questions about create_contact
Create HubSpot contact. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp MCP server in PolicyLayer and add a rule for create_contact: 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 Ncp. Nothing to install.
create_contact 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 create_contact 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 create_contact. 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.
create_contact is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue