AI agents call search_pubmed_key_words to retrieve information from PubMed-MCP-Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches PubMed by keywords, which is a read-only query operation with no side effects. It retrieves data without modifying, deleting, or executing code. The context of the server (public scientific literature access) and the pattern of sibling tools confirm this is a safe read operation. Confidence is high despite the empty description because the name and server context are sufficiently clear.
From the tool's definition Tool name 'search_pubmed_key_words' indicates a search operation. Sibling tools include 'search_pubmed_advanced', 'get_pubmed_article_metadata', and 'download_pubmed_pdf', all of which are read-only retrieval operations.
Documented attack patterns abuse exactly the kind of access search_pubmed_key_words gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PubMed-MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_pubmed_key_words:
{
"version": "1",
"default": "deny",
"tools": {
"search_pubmed_key_words": {}
}
} search_pubmed_key_words 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.
search_pubmed_key_words. It is categorised as a Read tool in the PubMed-MCP-Server MCP Server, which means it retrieves data without modifying state.
Register the PubMed-MCP-Server MCP server in PolicyLayer and add a rule for search_pubmed_key_words: 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-MCP-Server. Nothing to install.
search_pubmed_key_words 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 search_pubmed_key_words 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 search_pubmed_key_words. 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.
search_pubmed_key_words is provided by the PubMed-MCP-Server MCP server (jackkuo666/pubmed-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PubMed-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.
4 PubMed-MCP-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.