manage_tests

A other tool on the Kestra Python MCP server.

SERVERKestra Python MCP Server SOURCEkestra-io/mcp-server-python

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kestra-io-mcp-server-python/manage-tests.md

WHAT IT DOES

What manage_tests does on Kestra Python MCP Server

AI agents call manage_tests as a supporting operation in Kestra Python MCP Server workflows.

RISK

Why manage_tests is rated Low

The description is empty and uninformative. 'manage_tests' could imply reading, writing, executing, or destructive operations depending on implementation. Based on the name alone and the context of a Kestra workflow server, it likely involves creating/updating/deleting test configurations. Given the ambiguity, 'Write' or 'Execute' are plausible, but confidence is very low.

From the tool's definition Tool name is 'manage_tests' with an empty description. No description provided to clarify what operations are performed.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs manage_tests safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Kestra Python MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For manage_tests, this is the rule to start with:

manage_tests Rate-limited

manage_tests gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "manage_tests": {
      "limits": [
        {
          "counter": "manage_tests_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Kestra Python MCP Server, apply this rule, and every manage_tests call is checked against it from then on.

FAQ

Questions about manage_tests

What does the manage_tests tool do? +

manage_tests is a other tool on the Kestra Python MCP Server MCP server. It is categorised as a Other tool in the Kestra Python MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on manage_tests? +

Register the Kestra Python MCP Server MCP server in PolicyLayer and add a rule for manage_tests: 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 Kestra Python MCP Server. Nothing to install.

What risk level is manage_tests? +

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

Can I rate-limit manage_tests? +

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

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

manage_tests is provided by the Kestra Python MCP Server MCP server (kestra-io/mcp-server-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Kestra Python MCP Server, and thousands of servers like it.

This server

All 39 Kestra Python MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →