在知識庫中搜索相關內容
AI agents call search_knowledge to retrieve information from Notion Knowledge MCP Server 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 a knowledge base without side effects. It fits the Read category as it performs a search operation to find information, analogous to search/query/fetch operations. The low severity reflects that searching a knowledge base has minimal risk of harm even if misused—it cannot modify data, execute code, or cause financial impact.
From the tool's definition Tool name 'search_knowledge' and description indicate searching/querying knowledge base content ('搜索相關內容' = 'search related content'). No modification, deletion, or execution of external operations described.
Attacks that exploit this kind of access
在知識庫中搜索相關內容. It is categorised as a Read tool in the Notion Knowledge MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Notion Knowledge MCP Server MCP server in PolicyLayer and add a rule for search_knowledge: 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 Notion Knowledge MCP Server. Nothing to install.
search_knowledge 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_knowledge 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_knowledge. 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_knowledge is provided by the Notion Knowledge MCP Server MCP server (yuhuanhsu/notion-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 →