AI agents call list_groups to retrieve information from Folk 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 name 'list_groups' follows standard read-only naming conventions (list/enumerate operations). It is positioned alongside other read tools (browse_*) and contrasts with write operations (add_*) and destructive operations (delete_*) on this server. Even with an empty description, the semantic meaning of 'list' combined with the server's CRM context indicates this retrieves group data without side effects.
From the tool's definition Tool name 'list_groups' indicates a retrieval operation. Context shows sibling tools include browse_companies and browse_people which are read operations.
Documented attack patterns abuse exactly the kind of access list_groups gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Folk CRM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_groups:
{
"version": "1",
"default": "deny",
"tools": {
"list_groups": {}
}
}list_groups 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_groups. It is categorised as a Read tool in the Folk CRM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Folk CRM MCP Server MCP server in PolicyLayer and add a rule for list_groups: 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 Folk CRM MCP Server. Nothing to install.
list_groups 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_groups 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_groups. 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_groups is provided by the Folk CRM MCP Server MCP server (nimblebraininc/mcp-folk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Folk 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.
20 Folk CRM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.