AI agents use update_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.
update_person modifies existing contact records reversibly. This is a Write operation (creates or modifies data reversibly), not Execute or Destructive. Severity is medium because misuse could corrupt customer relationship data, but changes are typically reversible and the blast radius is limited to individual contact records unless the tool supports bulk operations (unknown due to empty description).
From the tool's definition Tool name 'update_person' indicates modification of person records in Folk CRM. No description provided, but context shows sibling tools include 'add_person' and 'delete_person', confirming this operates on CRM contact data.
Documented attack patterns abuse exactly the kind of access update_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 update_person:
{
"version": "1",
"default": "deny",
"tools": {
"update_person": {
"limits": [
{
"counter": "update_person_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_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.
update_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 update_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.
update_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 update_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 update_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.
update_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.