Count how many contacts match optional criteria. Returns only the count, not the contact records. This is the correct tool when you need to know how many contacts exist or match a filter — do not use search_contacts for counting.
AI agents call get_contact_count to retrieve information from Ontraport 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 aggregate metadata (a count) from the CRM without modifying, executing, or deleting any data. It is a read-only query operation. Severity is low because exposing contact counts presents minimal risk — enumeration of contact volume is not sensitive enough to warrant higher severity, though in some compliance contexts it could warrant medium.
From the tool's definition Tool description states it 'Count[s] how many contacts match optional criteria' and 'Returns only the count, not the contact records.' This is an introspection/query operation with no side effects.
Attacks that exploit this kind of access
Count how many contacts match optional criteria. Returns only the count, not the contact records. This is the correct tool when you need to know how many contacts exist or match a filter — do not use search_contacts for counting. It is categorised as a Read tool in the Ontraport MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Ontraport MCP Server MCP server in PolicyLayer and add a rule for get_contact_count: 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 Ontraport MCP Server. Nothing to install.
get_contact_count 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_contact_count 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_contact_count. 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_contact_count is provided by the Ontraport MCP Server MCP server (landonray/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 →