store.vector-query
STORE: nearest-neighbor search over vectors you upserted in...
This record as markdown: /tools/io-github-2s-io-mcp/store.vector-query.md
What store.vector-query does on Mcp
AI agents call store.vector-query 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.vector-query is rated Low
This is a query operation that searches and retrieves data from a vector database. It performs a read-only operation (nearest-neighbor search) without creating, modifying, deleting, or executing external code. The minimal blast radius and passive nature of the operation justify 'low' severity.
From the tool's definition Tool name 'vector-query' and description 'nearest-neighbor search over vectors' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs store.vector-query 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.vector-query, this is the rule to start with:
store.vector-query 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.vector-query call is checked against it from then on.
Questions about store.vector-query
STORE: nearest-neighbor search over vectors you upserted 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.vector-query: 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.vector-query 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.vector-query 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.vector-query. 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.vector-query 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