store.doc-get
STORE: fetch a stored document by id, scoped to YOUR wallet.
This record as markdown: /tools/io-github-2s-io-mcp/store.doc-get.md
What store.doc-get does on Mcp
AI agents call store.doc-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.doc-get is rated Low
This tool retrieves data (a stored document) without side effects or state changes. The wallet-scoping ensures the operation is isolated to the user's own resources, and 'fetch' is an archetypal Read operation. No Write, Execute, Destructive, or Financial impact is evident.
From the tool's definition Tool name 'doc-get' and description 'fetch a stored document by id' indicates a retrieval operation. The phrase 'scoped to YOUR wallet' confirms access control limiting results to the caller's own data with no modification or deletion capability.
Attacks that exploit this kind of access
The rule that runs store.doc-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.doc-get, this is the rule to start with:
store.doc-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.doc-get call is checked against it from then on.
Questions about store.doc-get
STORE: fetch a stored document by id, scoped to YOUR wallet. 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.doc-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.doc-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.doc-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.doc-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.doc-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