Find all contacts in a specific chapter
AI agents call search_contacts_by_chapter to retrieve information from CiviCRM 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 contact data filtered by chapter, matching the Read category definition (retrieves or queries data; no side effects). The severity is low because it only accesses existing data without modifying, deleting, or executing external operations. Confidence is high given the clear query semantics and passive data retrieval nature.
From the tool's definition Tool name 'search_contacts_by_chapter' and description 'Find all contacts in a specific chapter' indicate a query/retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Find all contacts in a specific chapter. It is categorised as a Read tool in the CiviCRM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CiviCRM MCP Server MCP server in PolicyLayer and add a rule for search_contacts_by_chapter: 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 CiviCRM MCP Server. Nothing to install.
search_contacts_by_chapter 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 search_contacts_by_chapter 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 search_contacts_by_chapter. 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.
search_contacts_by_chapter is provided by the CiviCRM MCP Server MCP server (johncallhub/civicrm-mcp-server). 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 →