Fetch detailed information for specific PubMed articles.
AI agents call get_article_details to retrieve information from NCBI Literature Search 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 existing scientific article metadata from PubMed without creating, modifying, deleting, or executing any operations. It is a straightforward read operation on a public database of scientific literature, posing minimal risk if misused by an AI agent.
From the tool's definition Tool name 'get_article_details' and description 'Fetch detailed information for specific PubMed articles' indicate data retrieval with no modification or execution capabilities.
Documented attack patterns abuse exactly the kind of access get_article_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and NCBI Literature Search MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_article_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_article_details": {}
}
} get_article_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.
Fetch detailed information for specific PubMed articles. It is categorised as a Read tool in the NCBI Literature Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NCBI Literature Search MCP Server MCP server in PolicyLayer and add a rule for get_article_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 NCBI Literature Search MCP Server. Nothing to install.
get_article_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_article_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_article_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_article_details is provided by the NCBI Literature Search MCP Server MCP server (vitorpavinato/ncbi-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from NCBI Literature Search 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.
12 NCBI Literature Search MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.