AI agents call ploomes_products_get 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 product information from the Ploomes CRM database without creating, modifying, or deleting any data. It is a straightforward query operation that fetches a single product record and optionally expands related fields. There are no side effects, and the operation is purely informational.
From the tool's definition Tool description states 'Get a single product by ID' with optional expansion of related entities. The verb 'Get' and the read-only nature of retrieval operations indicate no modification or deletion of data occurs.
Attacks that exploit this kind of access
Get a single product by ID from Ploomes CRM. Use $expand to include related entities like OtherProperties, Group, Family, or Parts. 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_products_get: 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_products_get 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_products_get 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_products_get. 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_products_get 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 →