AI agents use add_person to create or update resources in Folk CRM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Folk CRM MCP Server environment.
This tool creates new person/contact records in the CRM system, which is reversible data modification. It does not delete data (not Destructive), execute arbitrary code (not Execute), move money (not Financial), or merely retrieve data (not Read).
From the tool's definition Tool name 'add_person' combined with server description stating it 'support[s]...logging interactions, and setting follow-up tasks' indicates the tool creates new contact records in Folk CRM.
Documented attack patterns abuse exactly the kind of access add_person gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Folk CRM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_person:
{
"version": "1",
"default": "deny",
"tools": {
"add_person": {
"limits": [
{
"counter": "add_person_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_person 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.
Free to start. No card required.
add_person. It is categorised as a Write tool in the Folk CRM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Folk CRM MCP Server MCP server in PolicyLayer and add a rule for add_person: 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 Folk CRM MCP Server. Nothing to install.
add_person 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 add_person 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 add_person. 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.
add_person is provided by the Folk CRM MCP Server MCP server (nimblebraininc/mcp-folk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Folk CRM MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Folk CRM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.