ploomes_contacts_update · Ploomes MCP: Risk & Policy

WHAT IT DOES

What ploomes_contacts_update does on Ploomes

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

WHY IT NEEDS A POLICY

Why ploomes_contacts_update needs a policy

The tool modifies existing contact data in the CRM system but does not delete or destroy records. Updates are reversible—data can be changed back. This is a Write operation. Severity is medium because unauthorized contact updates could compromise CRM data integrity and lead to incorrect business decisions, but the impact is limited to a single contact record and is not irreversible.

From the tool's definition Tool name contains 'update' and description states 'Update an existing contact in Ploomes CRM by ID. Only provided fields are changed; omitted fields remain untouched.' This is a reversible modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ploomes_contacts_update Rate-limited

ploomes_contacts_update 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": {
    "ploomes_contacts_update": {
      "limits": [
        {
          "counter": "ploomes_contacts_update_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 Ploomes, so you can run agents against it safely.

FAQ

Questions about ploomes_contacts_update

What does the ploomes_contacts_update tool do? +

Update an existing contact in Ploomes CRM by ID. Only provided fields are changed; omitted fields remain untouched.\n\n. It is categorised as a Write tool in the Ploomes MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ploomes_contacts_update? +

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

What risk level is ploomes_contacts_update? +

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

Can I rate-limit ploomes_contacts_update? +

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

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

ploomes_contacts_update is provided by the Ploomes MCP server (ploomes-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.