manage_crm_deals · Pancake POS MCP: Risk & Policy

WHAT IT DOES

What manage_crm_deals does on Pancake POS MCP

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

WHY IT NEEDS A POLICY

Why manage_crm_deals needs a policy

The tool primarily creates and updates CRM deal records (reversible writes to a sales pipeline). While it includes delete capability, the context is managing business opportunity records rather than irreversible financial commitments or destructive data purges. An AI agent misusing this could create spurious deals or corrupt the sales pipeline, causing operational confusion and lost revenue tracking.

From the tool's definition Tool description states actions include 'list, get, create, update, delete' — the create and update operations modify CRM deal data reversibly, while delete is present but described alongside reversible operations in a business context (sales pipeline…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_crm_deals Rate-limited

manage_crm_deals 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": {
    "manage_crm_deals": {
      "limits": [
        {
          "counter": "manage_crm_deals_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 Pancake POS MCP, so you can run agents against it safely.

FAQ

Questions about manage_crm_deals

What does the manage_crm_deals tool do? +

Manage CRM deals (sales pipeline opportunities) in Pancake POS. Actions: list, get, create, update, delete. It is categorised as a Write tool in the Pancake POS MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on manage_crm_deals? +

Register the Pancake POS MCP server in PolicyLayer and add a rule for manage_crm_deals: 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 Pancake POS MCP. Nothing to install.

What risk level is manage_crm_deals? +

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

Can I rate-limit manage_crm_deals? +

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

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

manage_crm_deals is provided by the Pancake POS MCP server (svn4pro/pancake-pos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.