AI agents call ploomes_contacts_origins_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 reference data (contact/lead origin types) from the Ploomes CRM system. It does not create, modify, delete, or execute any operations—it only fetches and returns existing metadata. The blast radius of misuse is minimal, as an agent can only see origin options that are already defined in the system. This is a straightforward Read operation.
From the tool's definition Tool description states 'List available contact/lead origins' and 'Returns Id and Name'. The verb 'list' and the phrase 'List available' indicate a read-only query operation with no side effects.
Attacks that exploit this kind of access
List available contact/lead origins in Ploomes CRM (e.g., Website, Referral, Cold Call). Returns Id and Name. Use the returned Id as OriginId when creating contacts or deals. 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_contacts_origins_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_contacts_origins_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_contacts_origins_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_contacts_origins_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_contacts_origins_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 →