Get detailed information about an author from Google Scholar.
AI agents call get_author_info 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 queries and retrieves author information from Google Scholar—a read-only operation that does not create, modify, delete, or execute any code. No financial transactions or irreversible actions are involved. The blast radius of misuse is minimal, limited to information leakage of already-public scholarly metadata.
From the tool's definition Tool name 'get_author_info' and description 'Get detailed information about an author from Google Scholar' indicates retrieval of publicly available author metadata with no modification or side effects.
Attacks that exploit this kind of access
Get detailed information about an author from Google Scholar. 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 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 Unified Search MCP Server. 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 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 →