This record as markdown: /tools/io-github-devopam-mcpg/hybrid-search.md
What hybrid_search does on Mcpg
AI agents invoke hybrid_search to trigger actions in Mcpg. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why hybrid_search is rated High
The tool name suggests a hybrid search operation (likely combining vector/semantic and keyword search), which in a PostgreSQL context typically executes a complex query. Given sibling tools like analyze_hnsw_recall, analyze_rerank_ndcg, and analyze_reranker_lift, this server appears to be a vector/search-capable PostgreSQL server. A hybrid search likely executes a database query combining multiple search strategies.
From the tool's definition Tool name 'hybrid_search' on a production-grade PostgreSQL MCP server; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs hybrid_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 hybrid_search, this is the rule to start with:
hybrid_search stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 hybrid_search call is checked against it from then on.
Questions about hybrid_search
hybrid_search is a execute tool on the Mcpg MCP server. It is categorised as a Execute tool in the Mcpg MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcpg MCP server in PolicyLayer and add a rule for hybrid_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.
hybrid_search is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the hybrid_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 hybrid_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.
hybrid_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