Bulk-fetch up to 100 stored items by RID. Bodies are decoded automatically. Default as=metadata_only returns just RID/URL/timestamps to keep context lean; use as=html or as=markdown to include bodies.
AI agents call storage_bulk_get 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 retrieves or queries stored data with no side effects. The default behavior (metadata_only) and optional body inclusion (html/markdown) are read-only operations. No write, delete, execute, or financial operations are possible.
From the tool's definition Tool is a bulk-fetch operation that retrieves stored items by RID. Description explicitly states it 'returns just RID/URL/timestamps' (metadata) or includes bodies as html/markdown, with no modification or deletion capability mentioned.
Documented attack patterns abuse exactly the kind of access storage_bulk_get 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_bulk_get:
{
"version": "1",
"default": "deny",
"tools": {
"storage_bulk_get": {}
}
}storage_bulk_get 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.
Bulk-fetch up to 100 stored items by RID. Bodies are decoded automatically. Default as=metadata_only returns just RID/URL/timestamps to keep context lean; use as=html or as=markdown to include bodies. 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_bulk_get: 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_bulk_get 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_bulk_get 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_bulk_get. 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_bulk_get 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.