store.blob-get
STORE: download a file you uploaded with store.blob-put, in...
This record as markdown: /tools/io-github-2s-io-mcp/store.blob-get.md
What store.blob-get does on Mcp
AI agents call store.blob-get to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why store.blob-get is rated Low
This tool retrieves or queries data (a blob/file) that was previously uploaded. It has no side effects—it does not create, modify, delete, or execute anything. The operation is read-only and reversible. Despite the financial infrastructure context (USDC/Base/Solana), this specific tool performs only data retrieval, not financial transactions.
From the tool's definition Tool name 'store.blob-get' and description 'download a file you uploaded' indicates retrieval of previously stored data with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs store.blob-get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For store.blob-get, this is the rule to start with:
store.blob-get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every store.blob-get call is checked against it from then on.
Questions about store.blob-get
STORE: download a file you uploaded with store.blob-put, in. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for store.blob-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 Mcp. Nothing to install.
store.blob-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 store.blob-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 store.blob-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.
store.blob-get is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue