This record as markdown: /tools/io-github-devopam-mcpg/vector-search.md
What vector_search does on Mcpg
AI agents call vector_search to retrieve information from Mcpg without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why vector_search is rated Low
Vector search is a standard read-only database operation that queries a vector index to find similar vectors or nearest neighbors, returning results without side effects. The empty description lowers confidence slightly, but the tool name and server context (PostgreSQL analytical tools with sibling analyze_* functions) strongly indicate a read operation.
From the tool's definition Tool name 'vector_search' indicates a search operation. In database contexts, search operations retrieve matching records without modifying data.
Attacks that exploit this kind of access
The rule that runs vector_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vector_search, this is the rule to start with:
vector_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 Mcpg, apply this rule, and every vector_search call is checked against it from then on.
Questions about vector_search
vector_search is a read tool on the Mcpg MCP server. It is categorised as a Read tool in the Mcpg MCP Server, which means it retrieves data without modifying state.
Register the Mcpg MCP server in PolicyLayer and add a rule for vector_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 Mcpg. Nothing to install.
vector_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 vector_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 vector_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.
vector_search is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcpg, and thousands of servers like it.
This server
Across the catalogue