store.doc-search
STORE: full-text keyword search over documents you stored...
This record as markdown: /tools/io-github-2s-io-mcp/store.doc-search.md
What store.doc-search does on Mcp
AI agents call store.doc-search 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-search is rated Low
This tool only searches and retrieves data from stored documents. It has no side effects, does not modify or delete data, does not execute code or trigger external operations, and does not involve financial transactions. It fits squarely within the Read category as a search/query operation.
From the tool's definition Tool performs 'full-text keyword search over documents you stored' — a retrieval operation with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs store.doc-search 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-search, this is the rule to start with:
store.doc-search 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-search call is checked against it from then on.
Questions about store.doc-search
STORE: full-text keyword search over documents you stored. 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-search: 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-search 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-search 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-search. 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-search 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