AI agents call get_cached_article 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.
This is a pure read operation that retrieves previously cached article metadata from a session store. It has no side effects, does not modify data, and does not execute arbitrary code. The blast radius of misuse is minimal—an agent could retrieve article information it shouldn't have access to, but no irreversible actions or external operations are triggered.
From the tool's definition Tool name and description indicate retrieval of cached article details: 'get_cached_article' and '從 session 快取取得文章詳情' (retrieve article details from session cache). No modification, deletion, execution, or financial operations are involved.
Documented attack patterns abuse exactly the kind of access get_cached_article 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 get_cached_article:
{
"version": "1",
"default": "deny",
"tools": {
"get_cached_article": {}
}
}get_cached_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.
從 session 快取取得文章詳情。. 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 get_cached_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 Pubmed Search. Nothing to install.
get_cached_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 get_cached_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 get_cached_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.
get_cached_article 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.