Low Risk

expand_search_queries

expand_search_queries

How to control expand_search_queries ↓

What expand_search_queries does on Pubmed Search

AI agents call expand_search_queries 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.

Low Risk

Why expand_search_queries needs a policy

Based on context, this tool expands search queries to improve literature discovery—a read operation with no side effects. While the description is empty (lowering confidence slightly), the name and server purpose strongly indicate a retrieval/analysis function. The presence of destructive sibling tools (delete_pipeline) confirms this tool is distinct in purpose.

From the tool's definition Tool is named 'expand_search_queries' within a research literature search server context. The sibling tools include search, analyze, and build operations typical of read-only research workflows.

Documented attack patterns abuse exactly the kind of access expand_search_queries gives an agent:

How to control expand_search_queries

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 expand_search_queries:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "expand_search_queries": {}
  }
}

expand_search_queries is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Pubmed Search — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about expand_search_queries

What does the expand_search_queries tool do? +

expand_search_queries. It is categorised as a Read tool in the Pubmed Search MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on expand_search_queries? +

Register the Pubmed Search MCP server in PolicyLayer and add a rule for expand_search_queries: 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.

What risk level is expand_search_queries? +

expand_search_queries is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit expand_search_queries? +

Yes. Add a rate_limit block to the expand_search_queries 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.

How do I block expand_search_queries completely? +

Set action: deny in the PolicyLayer policy for expand_search_queries. 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.

What MCP server provides expand_search_queries? +

expand_search_queries 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.

Enforce policy on every Pubmed Search tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.