Search for academic authors by name on Semantic Scholar. Returns up to 5 matches with affiliations, paper count, total citation count, h-index, and profile URL. Keyless.
AI agents call get_author to retrieve information from Mcp Semanticscholar without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Author name to search for, e.g. "Yoshua Bengio". |
Parameters from the server's own tool schema.
This tool retrieves publicly available academic author metadata from Semantic Scholar. It performs a read-only query with no data modification, creation, deletion, or code execution. The response includes basic profile information (affiliations, metrics, URL) that is already public in the Semantic Scholar Academic Graph. The blast radius is minimal—misuse would only surface existing scholarly data.
From the tool's definition Search for academic authors by name on Semantic Scholar. Returns up to 5 matches with affiliations, paper count, total citation count, h-index, and profile URL.
Attacks that exploit this kind of access
Search for academic authors by name on Semantic Scholar. Returns up to 5 matches with affiliations, paper count, total citation count, h-index, and profile URL. Keyless. It is categorised as a Read tool in the Mcp Semanticscholar MCP Server, which means it retrieves data without modifying state.
get_author accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Semanticscholar MCP server in PolicyLayer and add a rule for get_author: 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 Mcp Semanticscholar. Nothing to install.
get_author 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 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. 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 is provided by the Mcp Semanticscholar MCP server (https://gateway.pipeworx.io/semanticscholar/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 →