Create a pipeline instance from a list of components
AI agents use instantiate_pipeline to create or update resources in Sktime — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sktime environment.
The tool creates a new pipeline object in memory by composing components. This is a reversible write/creation operation with no code execution, data deletion, or financial implications. Severity is medium because a misconfigured pipeline could lead to incorrect downstream model execution.
From the tool's definition Create a pipeline instance from a list of components
Documented attack patterns abuse exactly the kind of access instantiate_pipeline gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sktime, and nothing reaches the server without passing your rules. This is the rule we recommend for instantiate_pipeline:
{
"version": "1",
"default": "deny",
"tools": {
"instantiate_pipeline": {
"limits": [
{
"counter": "instantiate_pipeline_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}instantiate_pipeline stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a pipeline instance from a list of components. It is categorised as a Write tool in the Sktime MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sktime MCP server in PolicyLayer and add a rule for instantiate_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 Sktime. Nothing to install.
instantiate_pipeline is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the instantiate_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 instantiate_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.
instantiate_pipeline is provided by the Sktime MCP server (sktime/sktime-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sktime, 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.
24 Sktime tools catalogued and risk-classified — across an index of 43,000+ MCP servers.