store.doc-put
STORE: index a text document for full-text keyword search...
This record as markdown: /tools/io-github-2s-io-mcp/store.doc-put.md
What store.doc-put does on Mcp
AI agents use store.doc-put to create or update resources in Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp environment.
Why store.doc-put is rated Medium
This tool creates or modifies indexed documents in a persistent store, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely retrieve data (Read).
From the tool's definition Tool name 'store.doc-put' and description 'index a text document for full-text keyword search' indicate creation/storage of indexed documents.
Attacks that exploit this kind of access
The rule that runs store.doc-put 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-put, this is the rule to start with:
store.doc-put stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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-put call is checked against it from then on.
Questions about store.doc-put
STORE: index a text document for full-text keyword search. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP server in PolicyLayer and add a rule for store.doc-put: 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-put is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the store.doc-put 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-put. 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-put 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