Count documents in a collection with an optional filter.
AI agents call count to retrieve information from Askdb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Counting documents is a non-destructive, read-only operation. It retrieves metadata about existing data without creating, modifying, deleting, or executing code. Even with filter parameters, the operation remains observational. The sandbox isolation and field-level control mentioned in the server description further mitigate risk by limiting scope.
From the tool's definition The tool 'count' performs a counting operation on documents in a collection with optional filtering. The description explicitly states it 'counts' documents, which is a query operation that retrieves aggregated information without modifying data.
Documented attack patterns abuse exactly the kind of access count gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Askdb, and nothing reaches the server without passing your rules. This is the rule we recommend for count:
{
"version": "1",
"default": "deny",
"tools": {
"count": {}
}
}count 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.
Count documents in a collection with an optional filter. It is categorised as a Read tool in the Askdb MCP Server, which means it retrieves data without modifying state.
Register the Askdb MCP server in PolicyLayer and add a rule for 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 Askdb. Nothing to install.
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 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 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.
count is provided by the Askdb MCP server (mgorabbani/askdb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Askdb, 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.
10 Askdb tools catalogued and risk-classified — across an index of 43,000+ MCP servers.