Wyszukuje kontakt po adresie email
AI agents call fluentcrm_find_contact_by_email 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 performs a read-only lookup operation to find an existing contact record by email. It retrieves information but does not create, modify, delete, or execute any actions. This is a standard data retrieval operation with minimal risk if misused by an AI agent—the worst case would be information disclosure about contact existence, which is low severity.
From the tool's definition Tool name and description indicate it 'searches for a contact by email address' (fluentcrm_find_contact_by_email / Wyszukuje kontakt po adresie email). This is a query/lookup operation that retrieves data without modification or side effects.
Documented attack patterns abuse exactly the kind of access fluentcrm_find_contact_by_email 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_find_contact_by_email:
{
"version": "1",
"default": "deny",
"tools": {
"fluentcrm_find_contact_by_email": {}
}
}fluentcrm_find_contact_by_email 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.
Wyszukuje kontakt po adresie email. 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_find_contact_by_email: 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_find_contact_by_email 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_find_contact_by_email 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_find_contact_by_email. 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_find_contact_by_email 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.