AI agents call fluentcrm_custom_fields to retrieve information from FluentCRM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves (pobiera) custom field definitions from FluentCRM. This is a read-only operation analogous to a GET request. Low severity since it only exposes metadata/field configuration, not sensitive contact data.
From the tool's definition 'Pobiera pola niestandardowe' translates from Polish to 'Retrieves custom fields' — a read/fetch operation with no side effects
Documented attack patterns abuse exactly the kind of access fluentcrm_custom_fields gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and FluentCRM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for fluentcrm_custom_fields:
{
"version": "1",
"default": "deny",
"tools": {
"fluentcrm_custom_fields": {}
}
}fluentcrm_custom_fields 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.
Pobiera pola niestandardowe. It is categorised as a Read tool in the FluentCRM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FluentCRM MCP Server MCP server in PolicyLayer and add a rule for fluentcrm_custom_fields: 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 FluentCRM MCP Server. Nothing to install.
fluentcrm_custom_fields 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 fluentcrm_custom_fields 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 fluentcrm_custom_fields. 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.
fluentcrm_custom_fields is provided by the FluentCRM MCP Server MCP server (netflyapp/fluentcrm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from FluentCRM 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.
36 FluentCRM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.