Search workspace knowledge.
AI agents call knowledge_search to retrieve information from Chisel Knowledge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data from organized knowledge workspaces with no side effects. It fits the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The blast radius of misuse is minimal—an AI could only over-query or discover unintended information, not alter or execute anything. Low severity is appropriate for a pure search operation.
From the tool's definition Tool name 'knowledge_search' and description 'Search workspace knowledge' indicate a query operation that retrieves information from a knowledge base without modifying, deleting, or executing code. The verb 'search' is a classic read operation.
Attacks that exploit this kind of access
Search workspace knowledge. It is categorised as a Read tool in the Chisel Knowledge MCP MCP Server, which means it retrieves data without modifying state.
Register the Chisel Knowledge MCP server in PolicyLayer and add a rule for knowledge_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 Chisel Knowledge MCP. Nothing to install.
knowledge_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 knowledge_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 knowledge_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.
knowledge_search is provided by the Chisel Knowledge MCP server (teknologika/chisel-knowledge-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 →