AI agents invoke schedule_pipeline to trigger actions in Pubmed Search. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The name 'schedule_pipeline' implies triggering or scheduling an automated workflow or pipeline execution, which falls under Execute. The empty description lowers confidence. Given sibling tools include 'delete_pipeline', pipelines are real operational constructs, and scheduling one could have significant side effects depending on what the pipeline does. Severity is medium due to uncertainty about scope.
From the tool's definition Tool name 'schedule_pipeline' on a server with sibling tools like 'delete_pipeline' and 'configure_institutional_access' suggests triggering/scheduling automated pipeline execution.
Documented attack patterns abuse exactly the kind of access schedule_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 schedule_pipeline:
{
"version": "1",
"default": "deny",
"tools": {
"schedule_pipeline": {
"limits": [
{
"counter": "schedule_pipeline_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}schedule_pipeline stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
schedule_pipeline. It is categorised as a Execute tool in the Pubmed Search MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pubmed Search MCP server in PolicyLayer and add a rule for schedule_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.
schedule_pipeline is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the schedule_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 schedule_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.
schedule_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.