Low Risk

describe_estimator

Get detailed information about a specific sktime estimator

How to control describe_estimator ↓

What describe_estimator does on Sktime

AI agents call describe_estimator 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.

Low Risk

Why describe_estimator needs a policy

This tool queries and returns metadata or documentation about an estimator object. It performs no data modification, does not execute arbitrary code, and does not trigger external operations—it simply retrieves and presents information about available estimators in the sktime registry.

From the tool's definition Tool name 'describe_estimator' and description 'Get detailed information about a specific sktime estimator' indicate a retrieval operation with no side effects.

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

How to control describe_estimator

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "describe_estimator": {}
  }
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about describe_estimator

What does the describe_estimator tool do? +

Get detailed information about a specific sktime estimator. 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 describe_estimator? +

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

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

Can I rate-limit describe_estimator? +

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

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

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

Free to start. No card required.

24 Sktime tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.