Create a new person/contact in FUB
AI agents use createPerson to create or update resources in Follow Up Boss MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Follow Up Boss MCP Server environment.
This tool creates new contact records, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. However, it has medium severity because creating unauthorized or duplicate contacts could degrade CRM data quality, disrupt business processes, or enable social engineering if an agent creates fake contacts for malicious purposes.
From the tool's definition Tool name 'createPerson' and description 'Create a new person/contact in FUB' explicitly indicate creation of new data records in the CRM system.
Attacks that exploit this kind of access
Create a new person/contact in FUB. It is categorised as a Write tool in the Follow Up Boss MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Follow Up Boss MCP Server MCP server in PolicyLayer and add a rule for createPerson: 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 Follow Up Boss MCP Server. Nothing to install.
createPerson 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 createPerson 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 createPerson. 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.
createPerson is provided by the Follow Up Boss MCP Server MCP server (nerdsnipe-inc/follow-up-boss-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 →