Simplified hybrid mode query - Best for cross-domain queries. Combines both entity-focused and relationship-focused retrieval, ideal for comprehensive coverage spanning multiple knowledge areas.
AI agents call query_hybrid to retrieve information from Knowledge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a knowledge base to retrieve information. The hybrid query mode searches and retrieves data from the knowledge graph and vector embeddings but does not create, modify, delete, or execute external operations.
From the tool's definition Tool name 'query_hybrid' and description 'query' indicates data retrieval. Description states it 'Combines both entity-focused and relationship-focused retrieval' and is 'ideal for comprehensive coverage spanning multiple knowledge areas' — operations are…
Documented attack patterns abuse exactly the kind of access query_hybrid gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Knowledge, and nothing reaches the server without passing your rules. This is the rule we recommend for query_hybrid:
{
"version": "1",
"default": "deny",
"tools": {
"query_hybrid": {}
}
}query_hybrid is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Simplified hybrid mode query - Best for cross-domain queries. Combines both entity-focused and relationship-focused retrieval, ideal for comprehensive coverage spanning multiple knowledge areas. It is categorised as a Read tool in the Knowledge MCP Server, which means it retrieves data without modifying state.
Register the Knowledge MCP server in PolicyLayer and add a rule for query_hybrid: 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 Knowledge. Nothing to install.
query_hybrid 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 query_hybrid 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 query_hybrid. 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.
query_hybrid is provided by the Knowledge MCP server (olafgeibig/knowledge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Knowledge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Knowledge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.