AI agents call browse_people 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 'browse_people' and its position among sibling tools (find_person, find_people_in_group, browse_companies) strongly suggests it retrieves or lists people/contacts from the Folk CRM without modification. Browsing is a read-only operation. Confidence is slightly reduced due to empty description, but the naming pattern and context are sufficiently clear.
From the tool's definition Tool name 'browse_people' indicates a read operation following the pattern of sibling tool 'browse_companies' which retrieves entity data. No description provided, but naming convention and CRM context suggest data retrieval.
Documented attack patterns abuse exactly the kind of access browse_people 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 browse_people:
{
"version": "1",
"default": "deny",
"tools": {
"browse_people": {}
}
}browse_people 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.
browse_people. 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 browse_people: 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.
browse_people 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 browse_people 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 browse_people. 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.
browse_people 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.