AI agents call ploomes_deals_status_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.
The tool queries and returns a static list of deal status reference data from the Ploomes CRM system. It performs only read-only lookups of configuration/reference data (Id and Name fields) with no ability to create, modify, or delete information. This is a low-severity, high-confidence read operation typical of master-data lookups used to support filtering or validation in downstream operations.
From the tool's definition Tool description states 'List available deal statuses' and 'Returns Id and Name' — this is a retrieval operation with no mutation or side effects.
Attacks that exploit this kind of access
List available deal statuses in Ploomes CRM. Typically: 1=Open (Aberto), 2=Won (Ganho), 3=Lost (Perdido). Returns Id and Name. Use in $filter expressions like. 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_deals_status_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_deals_status_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_deals_status_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_deals_status_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_deals_status_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 →