Critical Risk →

delete_company

delete_company

How to control delete_company ↓

What delete_company does on Folk CRM MCP Server

AI agents call delete_company to permanently remove resources in Folk CRM MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_company needs a policy

Deletion of company records from a CRM system is irreversible and constitutes data loss. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The severity is high because deleting companies could impact business relationships, customer data, and operational continuity.

From the tool's definition Tool name 'delete_company' indicates irreversible deletion of company records. Description is empty, but the name and context (Folk CRM data management) clearly indicate this removes data that cannot be restored.

Documented attack patterns abuse exactly the kind of access delete_company gives an agent:

How to control delete_company

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 delete_company:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_company"
  ]
}

delete_company disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Folk CRM MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_company

What does the delete_company tool do? +

delete_company. It is categorised as a Destructive tool in the Folk CRM MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_company? +

Register the Folk CRM MCP Server MCP server in PolicyLayer and add a rule for delete_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.

What risk level is delete_company? +

delete_company is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_company? +

Yes. Add a rate_limit block to the delete_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.

How do I block delete_company completely? +

Set action: deny in the PolicyLayer policy for delete_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.

What MCP server provides delete_company? +

delete_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.

Enforce policy on every Folk CRM MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.