AI agents call get_person_details 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 personal contact details from the Folk CRM system with no side effects. The 'get_' naming convention and context of read operations (browse, find) in sibling tools indicate a data retrieval function. No modifications, deletions, or external operations are implied.
From the tool's definition Tool name 'get_person_details' combined with server description stating it 'Enables AI assistants to manage Folk CRM data, including contacts, companies, notes, and reminders' and 'supports searching for entities'.
Documented attack patterns abuse exactly the kind of access get_person_details 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 get_person_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_person_details": {}
}
}get_person_details 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.
get_person_details. 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 get_person_details: 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.
get_person_details 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 get_person_details 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 get_person_details. 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.
get_person_details 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.