AI agents call list_contacts_by_organization to retrieve information from CRM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs data retrieval filtered by organization, consistent with the 'Read' category (search, list, get, fetch). It has no destructive, write, execute, or financial impact. Confidence is slightly reduced due to the empty description, but the name and server functionality make the classification clear.
From the tool's definition Tool name 'list_contacts_by_organization' indicates a retrieval/query operation. The description is empty, but the name and server context (CRM with CRUD operations) strongly suggest this lists or filters existing contacts—a read-only operation with no side…
Documented attack patterns abuse exactly the kind of access list_contacts_by_organization gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CRM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_contacts_by_organization:
{
"version": "1",
"default": "deny",
"tools": {
"list_contacts_by_organization": {}
}
}list_contacts_by_organization is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
list_contacts_by_organization. It is categorised as a Read tool in the CRM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CRM MCP Server MCP server in PolicyLayer and add a rule for list_contacts_by_organization: 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 CRM MCP Server. Nothing to install.
list_contacts_by_organization 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 list_contacts_by_organization 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 list_contacts_by_organization. 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.
list_contacts_by_organization is provided by the CRM MCP Server MCP server (nxt3d/mcp-crm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CRM MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 CRM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.