Retrieve a single stored page from Crawlbase Cloud Storage by RID or URL. Only works for pages previously crawled with store=true. Returns the raw JSON record by default; pass as=html to return just the body, or as=markdown to convert it.
AI agents call storage_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 previously stored web content from cloud storage in various formats (JSON, HTML, or Markdown). It performs a read-only query operation with no side effects, no data modification, and no code execution. The only parameter variation is the output format (as=html, as=markdown), which does not change the underlying data.
From the tool's definition Tool name is 'storage_get' and description states 'Retrieve a single stored page' and 'Returns the raw JSON record'. The action is retrieval only ('Retrieve', 'return'), with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access storage_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_get:
{
"version": "1",
"default": "deny",
"tools": {
"storage_get": {}
}
}storage_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.
Retrieve a single stored page from Crawlbase Cloud Storage by RID or URL. Only works for pages previously crawled with store=true. Returns the raw JSON record by default; pass as=html to return just the body, or as=markdown to convert it. 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_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_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_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_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_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.