AI agents call find_person 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.
This tool retrieves or searches for person data from the Folk CRM system. The 'find_' prefix, combined with the server's stated capability to support 'searching for entities' and the pattern of sibling tools that clearly perform reads (browse_*) and writes (add_*) and destructive actions (delete_*), indicates this is a read-only query operation with no side effects.
From the tool's definition Tool name 'find_person' combined with server description stating 'searching for entities' and context of other tools like 'browse_companies', 'browse_people', 'find_companies_in_group', 'find_company' all indicating query/search operations without…
Documented attack patterns abuse exactly the kind of access find_person 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 find_person:
{
"version": "1",
"default": "deny",
"tools": {
"find_person": {}
}
}find_person 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.
find_person. 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 find_person: 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.
find_person 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 find_person 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 find_person. 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.
find_person 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.