AI agents call list_resolver_presets 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.
The tool appears to retrieve preset configurations for resolvers (likely document resolution mechanisms in an academic database context). 'List' operations are non-destructive queries that retrieve data without side effects. Although the description is uninformative, the verb 'list' combined with the server's purpose of providing research assistance indicates a retrieval function.
From the tool's definition Tool name 'list_resolver_presets' uses the verb 'list', which retrieves or enumerates configuration presets without modification. The description is empty, but the naming pattern suggests a read-only query operation.
Documented attack patterns abuse exactly the kind of access list_resolver_presets 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 list_resolver_presets:
{
"version": "1",
"default": "deny",
"tools": {
"list_resolver_presets": {}
}
}list_resolver_presets 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.
list_resolver_presets. 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 list_resolver_presets: 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.
list_resolver_presets 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_resolver_presets 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_resolver_presets. 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_resolver_presets 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.