generate_test
A other tool on the Kestra Python MCP server.
This record as markdown: /tools/kestra-io-mcp-server-python/generate-test.md
What generate_test does on Kestra Python MCP Server
AI agents call generate_test as a supporting operation in Kestra Python MCP Server workflows.
Why generate_test is rated Low
With no description available, the tool's behavior can only be guessed from its name. 'generate_test' likely creates test cases or test configurations for Kestra flows, which would be a Write operation. However, given the empty description, confidence is very low. Defaulting to Other due to insufficient information, with a low severity since test generation is typically a low-risk operation.
From the tool's definition Tool name is 'generate_test' but description is empty or uninformative
Attacks that exploit this kind of access
The rule that runs generate_test 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 generate_test, this is the rule to start with:
generate_test gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Kestra Python MCP Server, apply this rule, and every generate_test call is checked against it from then on.
Questions about generate_test
generate_test 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.
Register the Kestra Python MCP Server MCP server in PolicyLayer and add a rule for generate_test: 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.
generate_test is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the generate_test 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.
Set action: deny in the PolicyLayer policy for generate_test. 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.
generate_test 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.
More on Kestra Python MCP Server, and thousands of servers like it.
This server
Across the catalogue