Search Google Scholar for academic papers.
AI agents call search_google_scholar to retrieve information from Unified Search 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 academic paper metadata from Google Scholar, a read-only operation. It has no side effects, does not modify data, execute code, or incur financial costs. The blast radius of misuse is minimal—an agent might retrieve irrelevant or excessive results, but cannot cause data loss, security breaches, or financial harm.
From the tool's definition Tool name 'search_google_scholar' and description 'Search Google Scholar for academic papers' indicate a query operation that retrieves data without modification, deletion, or code execution.
Attacks that exploit this kind of access
Search Google Scholar for academic papers. It is categorised as a Read tool in the Unified Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Unified Search MCP Server MCP server in PolicyLayer and add a rule for search_google_scholar: 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 Unified Search MCP Server. Nothing to install.
search_google_scholar 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_google_scholar 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_google_scholar. 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_google_scholar is provided by the Unified Search MCP Server MCP server (jdeun/unified-search-mcp-server). 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 →