Delete a saved pipeline configuration and its execution history.
AI agents call delete_pipeline to permanently remove resources in Pubmed Search — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The delete_pipeline tool permanently removes stored pipeline configurations and their execution history without apparent recovery mechanism. This is a destructive operation that cannot be undone and could impact reproducibility of research workflows.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a saved pipeline configuration and its execution history' — this is irreversible data destruction affecting both configuration state and historical records.
Documented attack patterns abuse exactly the kind of access delete_pipeline 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 delete_pipeline:
{
"version": "1",
"default": "deny",
"hide": [
"delete_pipeline"
]
}delete_pipeline disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a saved pipeline configuration and its execution history. It is categorised as a Destructive tool in the Pubmed Search MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pubmed Search MCP server in PolicyLayer and add a rule for delete_pipeline: 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.
delete_pipeline is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_pipeline 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 delete_pipeline. 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.
delete_pipeline 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.