search_kb
Keyword search across a board
This record as markdown: /tools/ai-featureboard-featureboard/search-kb.md
What search_kb does on FeatureBoard
AI agents call search_kb to retrieve information from FeatureBoard without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_kb is rated Low
This tool performs a search operation, which is a read-only retrieval action. It does not create, modify, delete, or execute operations—it merely queries and returns results from the knowledge base. Low severity because search operations have minimal blast radius and no side effects.
From the tool's definition Tool name 'search_kb' and description 'Keyword search across a board' indicate querying/searching functionality with no modification of data.
Attacks that exploit this kind of access
The rule that runs search_kb safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_kb, this is the rule to start with:
search_kb 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 FeatureBoard, apply this rule, and every search_kb call is checked against it from then on.
Questions about search_kb
Keyword search across a board. It is categorised as a Read tool in the FeatureBoard MCP Server, which means it retrieves data without modifying state.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for search_kb: 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 FeatureBoard. Nothing to install.
search_kb 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 search_kb 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 search_kb. 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.
search_kb is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FeatureBoard, and thousands of servers like it.
This server
Across the catalogue