ploomes_orders_update · Ploomes MCP: Risk & Policy

WHAT IT DOES

What ploomes_orders_update does on Ploomes

AI agents use ploomes_orders_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_orders_update needs a policy

This tool modifies existing order records in a CRM system. While updates are reversible (unlike deletions), they can have significant business impact—orders in a CRM often trigger financial processes, inventory management, or customer workflows. The severity is high because misuse could corrupt critical business data or trigger unintended actions downstream.

From the tool's definition Tool description states 'Update an existing order in Ploomes CRM by ID. Only provided fields are changed.' The verb 'Update' and the operation of modifying existing records in a CRM system indicate a write operation that reversibly changes data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ploomes_orders_update Rate-limited

ploomes_orders_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_orders_update": {
      "limits": [
        {
          "counter": "ploomes_orders_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_orders_update

What does the ploomes_orders_update tool do? +

Update an existing order in Ploomes CRM by ID. Only provided fields are changed. 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_orders_update? +

Register the Ploomes MCP server in PolicyLayer and add a rule for ploomes_orders_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_orders_update? +

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

Can I rate-limit ploomes_orders_update? +

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

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

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