Retrieve a Google Scholar author profile and top publications by author name.
AI agents call get_author_info to retrieve information from ScholarMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval with no side effects—it queries Google Scholar to fetch author information and publication lists. It does not modify, delete, or execute any operations. The data retrieved is public academic information. Classification as Read is appropriate, with low severity since misuse would only result in excessive queries against a public service, not data loss or security compromise.
From the tool's definition Tool name 'get_author_info' and description 'Retrieve a Google Scholar author profile and top publications' indicate a read-only operation that queries and retrieves publicly available author profile data and publication metadata.
Documented attack patterns abuse exactly the kind of access get_author_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ScholarMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_author_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_author_info": {}
}
}get_author_info 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.
Retrieve a Google Scholar author profile and top publications by author name. It is categorised as a Read tool in the ScholarMCP MCP Server, which means it retrieves data without modifying state.
Register the Scholar MCP server in PolicyLayer and add a rule for get_author_info: 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 ScholarMCP. Nothing to install.
get_author_info 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 get_author_info 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 get_author_info. 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.
get_author_info is provided by the Scholar MCP server (lstudlo/scholarmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ScholarMCP, 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.
10 ScholarMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.