release_data_handle

THE RISK

Critical Risk

Why release_data_handle needs a policy

Releasing a data handle and freeing memory is an irreversible operation — once the handle is released and memory freed, the data reference is gone and cannot be recovered without re-loading or re-computing it. This qualifies as Destructive. Severity is medium because it affects in-memory state rather than persistent storage, but misuse could cause data loss within a workflow.

From the tool's definition Release a data handle and free memory

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

POLICY

How to control release_data_handle

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "release_data_handle"
  ]
}

release_data_handle disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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.

RESTRICT 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. 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 Write format_time_series Automatically format time series data (frequency, duplicates, missing values)

All 24 Sktime tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Sktime → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about release_data_handle

What does the release_data_handle tool do? +

Release a data handle and free memory. It is categorised as a Destructive tool in the Sktime MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on release_data_handle? +

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

release_data_handle is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit release_data_handle? +

Yes. Add a rate_limit block to the release_data_handle 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 release_data_handle completely? +

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

release_data_handle 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 →