Count how many records exist in any object collection matching optional criteria. Returns only the count, not the records. For contacts specifically, you can also use get_contact_count (objectID 0). Use this for pagination planning or dashboard-style counts on any object type.
AI agents call get_collection_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.
get_collection_count performs a read-only query operation. It retrieves statistical information (record counts) matching optional criteria, suitable for pagination planning and dashboard display. No data is created, modified, deleted, or executed. The tool has minimal blast radius if misused by an AI agent, as it cannot alter system state or trigger external operations.
From the tool's definition Tool description explicitly states it 'Count how many records exist' and 'Returns only the count, not the records.' This is a query operation with no side effects—it retrieves aggregate metadata without modifying, deleting, or executing actions.
Attacks that exploit this kind of access
Count how many records exist in any object collection matching optional criteria. Returns only the count, not the records. For contacts specifically, you can also use get_contact_count (objectID 0). Use this for pagination planning or dashboard-style counts on any object type. 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_collection_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_collection_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_collection_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_collection_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_collection_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 →