kb_search

A read tool on the Container- MCP server.

SERVERContainer-MCP SOURCE54rt1n/container-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/54rt1n-container-mcp/kb-search.md

WHAT IT DOES

What kb_search does on Container-MCP

AI agents call kb_search to retrieve information from Container-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why kb_search is rated Low

Based on the tool name 'kb_search', this appears to be a read-only operation that queries a knowledge base and returns results without side effects. While the empty description reduces confidence slightly, the semantic meaning of 'search' in this context implies data retrieval. Confidence is not higher due to the lack of explicit documentation confirming no write or execute capabilities.

From the tool's definition Tool name is 'kb_search' which typically indicates a search/query operation against a knowledge base. No description provided, but the naming convention and position among knowledge base tools (kb_create_document, kb_manage, kb_read) suggest retrieval without…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs kb_search safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Container-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kb_search, this is the rule to start with:

kb_search Allowed

kb_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kb_search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Container-MCP, apply this rule, and every kb_search call is checked against it from then on.

FAQ

Questions about kb_search

What does the kb_search tool do? +

kb_search is a read tool on the Container MCP server. It is categorised as a Read tool in the Container-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on kb_search? +

Register the Container 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 Container-MCP. Nothing to install.

What risk level is kb_search? +

kb_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit kb_search? +

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.

How do I block kb_search completely? +

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.

What MCP server provides kb_search? +

kb_search is provided by the Container MCP server (54rt1n/container-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Container, and thousands of servers like it.

This server

All 27 Container tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →