search_google_scholar_key_words
AI agents call search_google_scholar_key_words to retrieve information from Google-Scholar-MCP-Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches for academic papers using keywords, which is a read-only operation that retrieves data without side effects. Google Scholar search is a standard information retrieval service. The blast radius of misuse is minimal—incorrect searches waste queries or return irrelevant results, but cannot modify data, execute code, or incur financial obligations.
From the tool's definition Tool name 'search_google_scholar_key_words' and server description indicating 'search and access Google Scholar papers' indicates a query/retrieval operation. The empty tool description is consistent with a straightforward search function.
Documented attack patterns abuse exactly the kind of access search_google_scholar_key_words gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google-Scholar-MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_google_scholar_key_words:
{
"version": "1",
"default": "deny",
"tools": {
"search_google_scholar_key_words": {}
}
}search_google_scholar_key_words is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
search_google_scholar_key_words. It is categorised as a Read tool in the Google-Scholar-MCP-Server MCP Server, which means it retrieves data without modifying state.
Register the Google-Scholar-MCP-Server MCP server in PolicyLayer and add a rule for search_google_scholar_key_words: 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 Google-Scholar-MCP-Server. Nothing to install.
search_google_scholar_key_words 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_key_words 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_key_words. 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_key_words is provided by the Google-Scholar-MCP-Server MCP server (jackkuo666/google-scholar-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google-Scholar-MCP-Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Google-Scholar-MCP-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.