Check if a pipeline composition is valid
AI agents call validate_pipeline to retrieve information from Sktime without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs validation and verification of pipeline configurations without creating, modifying, deleting, or executing any data or operations. It is purely informational, checking the syntactic or semantic correctness of a pipeline composition. No external operations are triggered, no data is altered, and no code execution occurs as a result of validation.
From the tool's definition Tool name 'validate_pipeline' and description 'Check if a pipeline composition is valid' indicate a validation/checking operation with no side effects. The verb 'check' and the absence of any modification language confirm this is a read-only operation.
Documented attack patterns abuse exactly the kind of access validate_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 validate_pipeline:
{
"version": "1",
"default": "deny",
"tools": {
"validate_pipeline": {}
}
}validate_pipeline 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.
Check if a pipeline composition is valid. It is categorised as a Read tool in the Sktime MCP Server, which means it retrieves data without modifying state.
Register the Sktime MCP server in PolicyLayer and add a rule for validate_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.
validate_pipeline 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 validate_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 validate_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.
validate_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.