manage_tests

THE RISK

Low Risk

Why manage_tests needs a policy

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.

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

POLICY

How to control manage_tests

PolicyLayer is an MCP gateway — it sits between your AI agents and Kestra Python MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_tests:

policy.json

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

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

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

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Kestra Python MCP Server tools

Destructive delete_execution_logs delete_execution_logs Destructive delete_flow_logs delete_flow_logs Execute force_run_execution Force run an execution only if it is in CREATED, PAUSED, or QUEUED state. Execute execute_flow execute_flow Execute restart_execution restart_execution Execute backfill_executions backfill_executions Execute change_taskrun_state change_taskrun_state Execute manage_executions manage_executions

All 39 Kestra Python MCP Server tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about manage_tests

What does the manage_tests tool do? +

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

Enforce policy on every Kestra Python MCP Server tool call.

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

CHECK YOUR STACK →