AI agents call ploomes_orders_stages_list to retrieve information from Ploomes without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries order stage metadata from the CRM with no side effects. It is a standard read operation that returns static reference data to inform other operations. No data is created, modified, deleted, or financial transactions are involved. The blast radius of misuse is negligible—an agent could only retrieve stage information already available in the system.
From the tool's definition Tool name contains 'list' and description states 'List available order stages' with no modification or deletion. Returns reference data (Id and Name) for downstream use in other operations.
Attacks that exploit this kind of access
List available order stages in Ploomes CRM. Returns Id and Name. Use the returned Id as StageId when creating or updating orders. It is categorised as a Read tool in the Ploomes MCP Server, which means it retrieves data without modifying state.
Register the Ploomes MCP server in PolicyLayer and add a rule for ploomes_orders_stages_list: 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_stages_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ploomes_orders_stages_list 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_stages_list. 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_stages_list 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 →