crm_upsert_company · Medicus CRM MCP Server MCP

WHAT IT DOES

What crm_upsert_company does on Medicus CRM MCP Server

AI agents use crm_upsert_company to create or update resources in Medicus CRM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Medicus CRM MCP Server environment.

WHY IT NEEDS A POLICY

Why crm_upsert_company needs a policy

This tool performs Create or Update operations on company data, which are reversible changes. It does not execute arbitrary code, delete data irreversibly, or involve financial transactions. The severity is medium because misuse could corrupt CRM data or create unauthorized company records, but the effects can be undone through subsequent updates or deletion by an authorized actor.

From the tool's definition Tool name 'crm_upsert_company' and description 'Create or update a company by name' indicate reversible modification of company records through an upsert operation (create if not exists, update if exists).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

crm_upsert_company Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "crm_upsert_company": {
      "limits": [
        {
          "counter": "crm_upsert_company_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Medicus CRM MCP Server, so you can run agents against it safely.

FAQ

Questions about crm_upsert_company

What does the crm_upsert_company tool do? +

Create or update a company by name. It is categorised as a Write tool in the Medicus CRM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on crm_upsert_company? +

Register the Medicus CRM MCP Server MCP server in PolicyLayer and add a rule for crm_upsert_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 Medicus CRM MCP Server. Nothing to install.

What risk level is crm_upsert_company? +

crm_upsert_company is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit crm_upsert_company? +

Yes. Add a rate_limit block to the crm_upsert_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 crm_upsert_company completely? +

Set action: deny in the PolicyLayer policy for crm_upsert_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 crm_upsert_company? +

crm_upsert_company is provided by the Medicus CRM MCP Server MCP server (soundrolling/crmmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.