Get the total number of documents in Crawlbase Cloud Storage.
AI agents call storage_count to retrieve information from Crawlbase MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple read operation—counting documents in cloud storage. It has no side effects, does not modify or delete data, does not execute code, and does not involve financial transactions. The blast radius of misuse is minimal; an agent could only enumerate storage size, which poses no risk to data integrity or system stability.
From the tool's definition Tool name 'storage_count' and description 'Get the total number of documents' indicate a retrieval operation that queries storage metadata without modifying, deleting, or executing anything.
Documented attack patterns abuse exactly the kind of access storage_count gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crawlbase MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for storage_count:
{
"version": "1",
"default": "deny",
"tools": {
"storage_count": {}
}
} storage_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.
Get the total number of documents in Crawlbase Cloud Storage. It is categorised as a Read tool in the Crawlbase MCP MCP Server, which means it retrieves data without modifying state.
Register the Crawlbase MCP server in PolicyLayer and add a rule for storage_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 Crawlbase MCP. Nothing to install.
storage_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 storage_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 storage_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.
storage_count is provided by the Crawlbase MCP server (crawlbase/crawlbase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crawlbase MCP, 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.
9 Crawlbase MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.