Semantic search over the Halyard docs. Returns chunks with a
AI agents call kb_search to retrieve information from Halyard Knowledge Base MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
kb_search is a read-only tool that searches and retrieves documentation chunks. It has no side effects, cannot modify data, execute code, or perform destructive actions. The search functionality is limited to querying an existing knowledge base, making it a standard Read category tool with low severity risk. Confidence is high because the description clearly indicates retrieval behavior only.
From the tool's definition Tool performs "Semantic search over the Halyard docs. Returns chunks" - a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
Semantic search over the Halyard docs. Returns chunks with a. It is categorised as a Read tool in the Halyard Knowledge Base MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Halyard Knowledge Base MCP Server MCP server in PolicyLayer and add a rule for kb_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 Halyard Knowledge Base MCP Server. Nothing to install.
kb_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 kb_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 kb_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.
kb_search is provided by the Halyard Knowledge Base MCP Server MCP server (mqfarooqi1/agentic-rag-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →