New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_flow_logs

A destructive tool on the Kestra Python MCP server.

SERVERKestra Python MCP Server SOURCEkestra-io/mcp-server-python
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kestra-io-mcp-server-python/delete-flow-logs.md

What delete_flow_logs does on Kestra Python MCP Server

AI agents call delete_flow_logs to permanently remove resources in Kestra Python MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_flow_logs is rated Critical

The 'delete' operation in the tool name indicates this is a destructive action that irreversibly removes log data. Although the description is empty (lowering confidence slightly), the explicit 'delete' verb in a logging/workflow management context clearly indicates data destruction.

From the tool's definition Tool name 'delete_flow_logs' explicitly contains 'delete', indicating irreversible removal of data. The sibling context shows this server manages Kestra workflows and their execution logs. Deletion of logs cannot be undone.

Questions about delete_flow_logs

What does the delete_flow_logs tool do? +

delete_flow_logs is a destructive tool on the Kestra Python MCP Server MCP server. It is categorised as a Destructive tool in the Kestra Python MCP Server 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 delete_flow_logs? +

Register the Kestra Python MCP Server MCP server in PolicyLayer and add a rule for delete_flow_logs: 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 delete_flow_logs? +

delete_flow_logs 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 delete_flow_logs? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Kestra Python MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.