AI agents call search_core_fulltext 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 tool performs a read-only search across fulltext academic databases (CORE is a major aggregator of open access research). Despite the empty description, the naming convention aligns with passive query/search functions in the sibling tools (e.g., analyze_search_query).
From the tool's definition Tool name 'search_core_fulltext' indicates a search operation querying academic fulltext content. No description provided, but search operations are passive retrieval of data without modification or side effects.
Documented attack patterns abuse exactly the kind of access search_core_fulltext 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 search_core_fulltext:
{
"version": "1",
"default": "deny",
"tools": {
"search_core_fulltext": {}
}
}search_core_fulltext 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_core_fulltext. 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 search_core_fulltext: 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.
search_core_fulltext 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_core_fulltext 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_core_fulltext. 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_core_fulltext 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.