get_semantic_scholar_citations_and_references
How to control get_semantic_scholar_citations_and_references ↓
AI agents call get_semantic_scholar_citations_and_references 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 and queries citation and reference metadata from Semantic Scholar's academic database with no side effects. It performs a read operation without creating, modifying, deleting, or executing anything. The empty description slightly lowers confidence, but the name, server context, and sibling tools all indicate safe information retrieval.
From the tool's definition Tool name indicates retrieval of citations and references; server description states it 'retrieves paper and author details, and fetch citations and references.' No modification, deletion, or execution capability implied.
Documented attack patterns abuse exactly the kind of access get_semantic_scholar_citations_and_references 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_citations_and_references:
{
"version": "1",
"default": "deny",
"tools": {
"get_semantic_scholar_citations_and_references": {}
}
}get_semantic_scholar_citations_and_references 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_citations_and_references. 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_citations_and_references: 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_citations_and_references 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_citations_and_references 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_citations_and_references. 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_citations_and_references 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.