Get detailed abstract information for a Scopus document (by EID).
AI agents call get_abstract_details 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.
The tool's purpose is to fetch and return abstract metadata from Scopus without any side effects. It is a read-only query operation that retrieves existing bibliographic data. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an agent could only access information already indexed in Scopus, with no capability to harm systems or data.
From the tool's definition Tool retrieves 'detailed abstract information for a Scopus document' by identifier (EID). No modifications, deletions, or external operations are performed. This is a data retrieval operation.
Documented attack patterns abuse exactly the kind of access get_abstract_details 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 get_abstract_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_abstract_details": {}
}
} get_abstract_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 detailed abstract information for a Scopus document (by EID). 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 get_abstract_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 UniArticles MCP Server. Nothing to install.
get_abstract_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_abstract_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_abstract_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_abstract_details 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.