get_semantic_scholar_author_details
AI agents call get_semantic_scholar_author_details to retrieve information from Semantic 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 retrieves author details from a public academic database (Semantic Scholar). It performs a query operation that returns information without modifying, executing code, or causing destructive changes. The pattern matches other Read category tools on the same server. Confidence is slightly reduced because the tool description is empty, but the name and context strongly indicate a simple retrieval operation.
From the tool's definition Tool name 'get_semantic_scholar_author_details' and server description indicate retrieval of author information from Semantic Scholar API.
Documented attack patterns abuse exactly the kind of access get_semantic_scholar_author_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Semantic Scholar MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_semantic_scholar_author_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_semantic_scholar_author_details": {}
}
}get_semantic_scholar_author_details 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.
get_semantic_scholar_author_details. It is categorised as a Read tool in the Semantic Scholar MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Semantic Scholar MCP Server MCP server in PolicyLayer and add a rule for get_semantic_scholar_author_details: 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 Semantic Scholar MCP Server. Nothing to install.
get_semantic_scholar_author_details 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_semantic_scholar_author_details 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_semantic_scholar_author_details. 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_semantic_scholar_author_details is provided by the Semantic Scholar MCP Server MCP server (jackkuo666/semanticscholar-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Semantic 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.
4 Semantic Scholar MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.