AI agents call knowledge_base to retrieve information from Scholar without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Given the server's stated purpose of 'Multi-source academic paper search, citation graph exploration, and PDF download' and the pattern of sibling tools (all read/search operations), 'knowledge_base' most likely retrieves or queries academic data without side effects. The empty description reduces confidence, but the server context and naming strongly suggest this is a Read operation.
From the tool's definition Tool named 'knowledge_base' with empty description; context indicates this is an academic research server with sibling tools like 'search_papers', 'read_paper', 'paper_info', and 'recommend_papers' that are all retrieval-focused operations.
Attacks that exploit this kind of access
knowledge_base. It is categorised as a Read tool in the Scholar MCP Server, which means it retrieves data without modifying state.
Register the Scholar MCP server in PolicyLayer and add a rule for knowledge_base: 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 Scholar. Nothing to install.
knowledge_base 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_base 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_base. 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_base is provided by the Scholar MCP server (liyux3/scholar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
knowledge_base is one line of Scholar's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →