Run FTS searches against knowledge/ and inbox/ for a given query and return results. Call this after reading an inbox file to check for overlap before deciding whether to compile new, extend, or skip.
AI agents call knowledge_get_dedupe_context 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 performs full-text search queries and returns matching results from existing knowledge bases. It retrieves and queries data without creating, modifying, deleting, or executing external operations. The blast radius of misuse is minimal—an agent could only retrieve information it should not see, not alter or destroy any data. This is a classic Read category operation.
From the tool's definition Tool description explicitly states "Run FTS searches against knowledge/ and inbox/" and "return results." The verb "searches" and "return" indicate data retrieval with no modification.
Attacks that exploit this kind of access
Run FTS searches against knowledge/ and inbox/ for a given query and return results. Call this after reading an inbox file to check for overlap before deciding whether to compile new, extend, or skip. 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_get_dedupe_context: 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_get_dedupe_context 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_get_dedupe_context 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_get_dedupe_context. 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_get_dedupe_context 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 →