Search for documents in Scopus using a query string.
AI agents call search_scopus to retrieve information from UniArticles 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 academic literature metadata from Scopus based on search parameters. It has no capability to modify, delete, or execute code. The worst-case misuse scenario is an AI agent performing excessive queries or retrieving sensitive academic information, both low-impact concerns. Consistent with sibling tools like search_arxiv, search_authors, and list_papers which are all read operations.
From the tool's definition Tool is described as 'Search for documents in Scopus using a query string.' The verb 'search' and the absence of any modification, deletion, or execution language indicate a query operation that retrieves data without side effects.
Documented attack patterns abuse exactly the kind of access search_scopus gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and UniArticles MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_scopus:
{
"version": "1",
"default": "deny",
"tools": {
"search_scopus": {}
}
}search_scopus 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.
Search for documents in Scopus using a query string. It is categorised as a Read tool in the UniArticles MCP Server MCP Server, which means it retrieves data without modifying state.
Register the UniArticles MCP Server MCP server in PolicyLayer and add a rule for search_scopus: 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 UniArticles MCP Server. Nothing to install.
search_scopus 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_scopus 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_scopus. 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_scopus is provided by the UniArticles MCP Server MCP server (thinktraveller/uniarticles_mcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from UniArticles 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.
15 UniArticles MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.