AI agents call ploomes_orders_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 order data from Ploomes CRM without creating, modifying, or deleting any records. It supports OData query patterns (filtering, sorting, pagination) typical of read-only API endpoints. The blast radius of misuse is minimal—an agent could retrieve sensitive business data, but cannot alter the system state. Classified as Read with low severity.
From the tool's definition Tool name and description both indicate retrieval operations: 'Search and list orders' with support for 'filtering, sorting, field selection, and pagination.' These are hallmarks of query/read operations with no modification or deletion capability.
Attacks that exploit this kind of access
Search and list orders in Ploomes CRM. Supports OData filtering, sorting, field selection, and pagination. Use $expand=OtherProperties to include custom fields. 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_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_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_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_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_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 →