List entity types that support custom fields in Ploomes CRM. Returns Id and Name. Known EntityId values: 1=Contact, 2=Deal, 4=Order, 5=Order Section, 7=Quote, 8=Quote Section, 10=Product, 12=Task, 14=Quote Product, 20=Order Product, 36=Interaction Record. Use these when filtering ploomes_fields_l...
AI agents call ploomes_fields_entities_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 metadata about entity types that support custom fields in Ploomes CRM. It performs a simple query operation with no side effects, no data modification, and no external execution. It is purely informational, returning static reference data to be used as input for other operations. This is a classic Read category operation with minimal risk.
From the tool's definition Tool name contains 'list' and description states it 'List entity types' and 'Returns Id and Name'. No mutation, deletion, or execution keywords present.
Attacks that exploit this kind of access
List entity types that support custom fields in Ploomes CRM. Returns Id and Name. Known EntityId values: 1=Contact, 2=Deal, 4=Order, 5=Order Section, 7=Quote, 8=Quote Section, 10=Product, 12=Task, 14=Quote Product, 20=Order Product, 36=Interaction Record. Use these when filtering ploomes_fields_list. 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_fields_entities_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_fields_entities_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_fields_entities_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_fields_entities_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_fields_entities_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 →