AI agents call search_authors 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.
This tool retrieves information about academic researchers from a database. It performs a search query without modifying data, executing code, or triggering side effects. Searching for publicly available author information poses minimal security risk to the system or data integrity. It fits the Read category as a straightforward information retrieval operation.
From the tool's definition Tool name 'search_authors' and description 'Search for academic authors/researchers' indicate a query operation with no modification or execution of external systems.
Attacks that exploit this kind of access
Search for academic authors/researchers. 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 search_authors: 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.
search_authors 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_authors 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_authors. 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_authors 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.
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 →