export_code

THE RISK

Low Risk

Why export_code needs a policy

The tool generates/exports code as output rather than executing it, modifying data, or causing side effects. It reads the current estimator/pipeline configuration and produces a Python code representation. The output is text/code that the user would then choose to run separately. Severity is low since misuse would at worst produce incorrect code, not directly cause harm.

From the tool's definition Export an estimator or pipeline as executable Python code

Documented attack patterns abuse exactly the kind of access export_code gives an agent:

POLICY

How to control export_code

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 export_code:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_code": {}
  }
}

export_code is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Sktime — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Sktime tools

Destructive cancel_job Cancel a running or pending background job. Destructive release_data_handle Release a data handle and free memory Execute evaluate_estimator Evaluate an estimator using cross-validation on a dataset Execute fit_predict Fit an estimator and generate predictions. Execute fit_predict_async Fit an estimator and generate predictions in the background. Execute fit_predict_classification Fit a time series classifier on training data and predict class labels on test data. Use w Execute fit_predict_regression Fit a time series regressor on training data and predict continuous target values on test Execute instantiate_estimator Create an estimator instance with given parameters

All 24 Sktime tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about export_code

What does the export_code tool do? +

Export an estimator or pipeline as executable Python code. It is categorised as a Read tool in the Sktime MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on export_code? +

Register the Sktime MCP server in PolicyLayer and add a rule for export_code: 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.

What risk level is export_code? +

export_code is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit export_code? +

Yes. Add a rate_limit block to the export_code 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.

How do I block export_code completely? +

Set action: deny in the PolicyLayer policy for export_code. 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.

What MCP server provides export_code? +

export_code 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.

Enforce policy on every Sktime tool call.

Start from Sktime, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →