AI agents use merge_search_results to create or update resources in Pubmed Search — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pubmed Search environment.
Merging search results is a reversible data operation that likely combines, organizes, or consolidates query outputs without deletion. The empty description lowers confidence, but the context of an academic research assistant and the naming pattern suggests this performs write-class aggregation rather than destruction, execution, or side effects. Confidence reduced due to lack of explicit documentation.
From the tool's definition Tool name 'merge_search_results' suggests combining or modifying search result sets. Description is empty, limiting certainty. Sibling tools like 'build_citation_tree' and 'build_research_timeline' indicate data transformation/aggregation functions.
Documented attack patterns abuse exactly the kind of access merge_search_results 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 merge_search_results:
{
"version": "1",
"default": "deny",
"tools": {
"merge_search_results": {
"limits": [
{
"counter": "merge_search_results_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}merge_search_results stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
merge_search_results. It is categorised as a Write tool in the Pubmed Search MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pubmed Search MCP server in PolicyLayer and add a rule for merge_search_results: 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.
merge_search_results is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the merge_search_results 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 merge_search_results. 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.
merge_search_results 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.