AI agents use ploomes_orders_create 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.
Creating orders is a write operation that modifies the CRM database by adding new records. While reversible (orders can typically be deleted or cancelled), this has moderate blast radius as an AI agent could create unwanted or duplicate orders, impacting business processes and data integrity.
From the tool's definition Tool name 'ploomes_orders_create' and description 'Create a new order in Ploomes CRM' explicitly indicate creation of new data (order records) in a reversible manner.
Attacks that exploit this kind of access
Create a new order in Ploomes CRM. ContactId is required. 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.
Register the Ploomes MCP server in PolicyLayer and add a rule for ploomes_orders_create: 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.
ploomes_orders_create 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 ploomes_orders_create 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 ploomes_orders_create. 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.
ploomes_orders_create 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.
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 →