AI agents call advanced_search to retrieve information from PubMed Advanced 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 or queries biomedical literature data from PubMed. Even though the description is empty, the naming pattern ('advanced_search'), the server's stated purpose ('searching, retrieving, and linking biomedical literature'), and the presence of sibling tools like 'batch_fetch_articles' and 'find_related_articles' all indicate this is a Read operation.
From the tool's definition Tool named 'advanced_search' on a PubMed literature retrieval server with sibling tools that fetch, retrieve, and search biomedical data. The 'advanced_search' naming convention and server purpose indicate querying/retrieval without modification or deletion.
Documented attack patterns abuse exactly the kind of access advanced_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PubMed Advanced MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for advanced_search:
{
"version": "1",
"default": "deny",
"tools": {
"advanced_search": {}
}
}advanced_search 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.
advanced_search. It is categorised as a Read tool in the PubMed Advanced MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PubMed Advanced MCP Server MCP server in PolicyLayer and add a rule for advanced_search: 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 Advanced MCP Server. Nothing to install.
advanced_search 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 advanced_search 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 advanced_search. 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.
advanced_search is provided by the PubMed Advanced MCP Server MCP server (suyashekhande/pubmed-mcp-advanced). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PubMed Advanced 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.
16 PubMed Advanced MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.