AI agents use update_company 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.
The tool modifies existing company records in the CRM system. This is a Write operation because updates are reversible changes to data (as opposed to Destructive deletes or Financial transfers). Severity is high because corrupting company data in a CRM affects business operations, customer relationships, and decision-making.
From the tool's definition Tool name is 'update_company' which modifies company data in Folk CRM. The server description indicates it 'manage[s] Folk CRM data, including contacts, companies, notes, and reminders.' Sibling tools include destructive operations (delete_company,…
Documented attack patterns abuse exactly the kind of access update_company 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_company:
{
"version": "1",
"default": "deny",
"tools": {
"update_company": {
"limits": [
{
"counter": "update_company_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_company 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_company. 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_company: 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_company 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_company 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_company. 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_company 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.