List all previously stored PubMed and PMC searches
AI agents call list_pubmed_searches to retrieve information from Enhanced PubMed 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 historical search records from a SQLite-backed search history without altering, deleting, or executing any operations. It is a straightforward query operation that returns existing data. The only minor consideration is that search history might contain user query patterns, but listing stored searches poses minimal risk compared to other tool categories.
From the tool's definition Tool name contains 'list' and description states 'List all previously stored PubMed and PMC searches' — a pure retrieval operation with no modification or deletion capability.
Attacks that exploit this kind of access
List all previously stored PubMed and PMC searches. It is categorised as a Read tool in the Enhanced PubMed MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced PubMed MCP Server MCP server in PolicyLayer and add a rule for list_pubmed_searches: 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 Enhanced PubMed MCP Server. Nothing to install.
list_pubmed_searches 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 list_pubmed_searches 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 list_pubmed_searches. 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.
list_pubmed_searches is provided by the Enhanced PubMed MCP Server MCP server (masa061580/enhanced-pubmed-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →