List FluentCRM contacts with filtering and pagination
AI agents call fcrm_list_contacts to retrieve information from FluentCommunity Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves contact information from FluentCRM without altering, deleting, or executing actions. It provides query and search capabilities only. The severity is low because listing contacts has minimal blast radius—the worst case is information disclosure of contact data that should already be accessible to authorized users in normal system operations.
From the tool's definition Tool name 'list_contacts' and description 'List FluentCRM contacts with filtering and pagination' indicate data retrieval with no modification. The verb 'list' combined with 'filtering and pagination' are characteristic Read operations.
Attacks that exploit this kind of access
List FluentCRM contacts with filtering and pagination. It is categorised as a Read tool in the FluentCommunity Manager MCP Server, which means it retrieves data without modifying state.
Register the FluentCommunity Manager MCP server in PolicyLayer and add a rule for fcrm_list_contacts: 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 FluentCommunity Manager. Nothing to install.
fcrm_list_contacts 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 fcrm_list_contacts 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 fcrm_list_contacts. 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.
fcrm_list_contacts is provided by the FluentCommunity Manager MCP server (wplaunchify/fluent-community-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →