AI agents call fetch_article_details to retrieve information from Pubmed Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves article metadata or details from academic databases without modifying, deleting, or executing external operations. This is a straightforward read operation with minimal blast radius—inappropriate use would only surface irrelevant or sensitive research papers, not cause data loss or financial harm.
From the tool's definition Tool name 'fetch_article_details' indicates data retrieval. Server context describes 'literature search and analysis across multiple academic databases,' confirming this is a query tool.
Documented attack patterns abuse exactly the kind of access fetch_article_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pubmed Search, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_article_details:
{
"version": "1",
"default": "deny",
"tools": {
"fetch_article_details": {}
}
}fetch_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_article_details. It is categorised as a Read tool in the Pubmed Search MCP Server, which means it retrieves data without modifying state.
Register the Pubmed Search MCP server in PolicyLayer and add a rule for fetch_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 Pubmed Search. Nothing to install.
fetch_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 fetch_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 fetch_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.
fetch_article_details is provided by the Pubmed Search MCP server (u9401066/pubmed-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pubmed Search, 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.
63 Pubmed Search tools catalogued and risk-classified — across an index of 43,000+ MCP servers.