Retrieve a full-text article record by identifier type (pii, doi, pubmed_id, eid) and value.
AI agents call retrieve_article 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 queries and returns academic article data based on identifiers (pii, doi, pubmed_id, eid). It has no side effects—it does not create, modify, delete, or execute operations. The operation is purely informational retrieval from academic databases, consistent with the Read category. Low severity because unauthorized article retrieval poses minimal direct harm compared to other categories.
From the tool's definition Tool description states 'Retrieve a full-text article record by identifier' with no mention of modification, deletion, or execution. The verb 'retrieve' and context of academic literature access indicate data retrieval only.
Documented attack patterns abuse exactly the kind of access retrieve_article 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 retrieve_article:
{
"version": "1",
"default": "deny",
"tools": {
"retrieve_article": {}
}
}retrieve_article 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.
Retrieve a full-text article record by identifier type (pii, doi, pubmed_id, eid) and value. 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 retrieve_article: 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.
retrieve_article 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 retrieve_article 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 retrieve_article. 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.
retrieve_article 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.