AI agents call get_company_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 company information from a CRM system without modifying, deleting, or executing any operations. It falls squarely into the Read category—a straightforward query that returns data. The severity is low because CRM contact/company data, while potentially sensitive, does not have direct destructive or financial consequences from retrieval alone.
From the tool's definition Tool name 'get_company_details' indicates a retrieval operation. The server description confirms it 'enables AI assistants to manage Folk CRM data' including searching for entities and the sibling tools show a pattern where 'browse_companies' and…
Documented attack patterns abuse exactly the kind of access get_company_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_company_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_company_details": {}
}
}get_company_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_company_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_company_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_company_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_company_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_company_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_company_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.