Manage CRM contacts in Pancake POS. Actions: list, get, create, update, delete. CRM pipeline: contacts → deals → activities.
AI agents use manage_crm_contacts 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.
Although this tool includes a 'delete' action which is destructive, the tool's primary focus—as evidenced by the action list order and CRM context—is managing contact data through creation and updates. Delete is mentioned but appears incidental to the core write operations.
From the tool's definition Tool description lists actions: 'list, get, create, update, delete.' The presence of 'delete' indicates destructive capability, but the primary documented operations are reversible (create, update).
Attacks that exploit this kind of access
Manage CRM contacts in Pancake POS. Actions: list, get, create, update, delete. CRM pipeline: contacts → deals → activities. 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.
Register the Pancake POS MCP server in PolicyLayer and add a rule for manage_crm_contacts: 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.
manage_crm_contacts 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 manage_crm_contacts 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 manage_crm_contacts. 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.
manage_crm_contacts 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →