AI agents call global_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 appears to search biomedical literature without side effects. While the description is empty (lowering confidence slightly), the server's stated purpose of enabling 'searching and retrieving' combined with the sibling tools all being read-only queries strongly indicates this is a Read operation that retrieves data without modification or destructive effects.
From the tool's definition Tool is named 'global_search' and exists within a PubMed literature retrieval server whose purpose is to 'search, retrieving, and linking biomedical literature.' Sibling tools are all read-only query operations (advanced_search, fetch_article_summary,…
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access global_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 global_search:
{
"version": "1",
"default": "deny",
"tools": {
"global_search": {}
}
}global_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.
global_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 global_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.
global_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 global_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 global_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.
global_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.