# delete_flow_logs A destructive tool on the Kestra Python MCP Server MCP server. Agent View of the PolicyLayer registry record for `delete_flow_logs`. HTML page: https://policylayer.com/tools/kestra-io-mcp-server-python/delete-flow-logs ## Facts - Tool: `delete_flow_logs` - Server: Kestra Python MCP Server (`kestra-io/mcp-server-python`) — https://policylayer.com/tools/kestra-io-mcp-server-python.md - Homepage: https://github.com/kestra-io/mcp-server-python - Risk category: Destructive (Critical risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Hidden ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "delete_flow_logs", "arguments": {} } } ``` ## 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 own 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." ## Use case 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. ## Recommended policy (PolicyLayer) Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Kestra Python MCP Server: ```json { "version": "1", "default": "deny", "hide": [ "delete_flow_logs" ] } ``` ## Other tools on Kestra Python MCP Server (38) - `delete_execution_logs` — Destructive — https://policylayer.com/tools/kestra-io-mcp-server-python/delete-execution-logs.md - `backfill_executions` — Execute — https://policylayer.com/tools/kestra-io-mcp-server-python/backfill-executions.md - `change_taskrun_state` — Execute — https://policylayer.com/tools/kestra-io-mcp-server-python/change-taskrun-state.md - `execute_flow` — Execute — https://policylayer.com/tools/kestra-io-mcp-server-python/execute-flow.md - `force_run_execution` — Execute — https://policylayer.com/tools/kestra-io-mcp-server-python/force-run-execution.md - `manage_executions` — Execute — https://policylayer.com/tools/kestra-io-mcp-server-python/manage-executions.md - `replay_execution` — Execute — https://policylayer.com/tools/kestra-io-mcp-server-python/replay-execution.md - `restart_execution` — Execute — https://policylayer.com/tools/kestra-io-mcp-server-python/restart-execution.md - `resume_execution` — Execute — https://policylayer.com/tools/kestra-io-mcp-server-python/resume-execution.md - `generate_app` — Other — https://policylayer.com/tools/kestra-io-mcp-server-python/generate-app.md - `generate_dashboard` — Other — https://policylayer.com/tools/kestra-io-mcp-server-python/generate-dashboard.md - `generate_test` — Other — https://policylayer.com/tools/kestra-io-mcp-server-python/generate-test.md - `manage_apps` — Other — https://policylayer.com/tools/kestra-io-mcp-server-python/manage-apps.md - `manage_group` — Other — https://policylayer.com/tools/kestra-io-mcp-server-python/manage-group.md - `manage_tests` — Other — https://policylayer.com/tools/kestra-io-mcp-server-python/manage-tests.md - `namespace_directory_action` — Other — https://policylayer.com/tools/kestra-io-mcp-server-python/namespace-directory-action.md - `namespace_file_action` — Other — https://policylayer.com/tools/kestra-io-mcp-server-python/namespace-file-action.md - `download_execution_logs` — Read — https://policylayer.com/tools/kestra-io-mcp-server-python/download-execution-logs.md - `find_flow` — Read — https://policylayer.com/tools/kestra-io-mcp-server-python/find-flow.md - `follow_execution_logs` — Read — https://policylayer.com/tools/kestra-io-mcp-server-python/follow-execution-logs.md - `get_execution_logs` — Read — https://policylayer.com/tools/kestra-io-mcp-server-python/get-execution-logs.md - `get_instance_info` — Read — https://policylayer.com/tools/kestra-io-mcp-server-python/get-instance-info.md - `list_executions` — Read — https://policylayer.com/tools/kestra-io-mcp-server-python/list-executions.md - `list_flows_in_namespace` — Read — https://policylayer.com/tools/kestra-io-mcp-server-python/list-flows-in-namespace.md - `list_flows_with_triggers` — Read — https://policylayer.com/tools/kestra-io-mcp-server-python/list-flows-with-triggers.md - `list_namespace_dependencies` — Read — https://policylayer.com/tools/kestra-io-mcp-server-python/list-namespace-dependencies.md - `list_namespaces` — Read — https://policylayer.com/tools/kestra-io-mcp-server-python/list-namespaces.md - `search_apps` — Read — https://policylayer.com/tools/kestra-io-mcp-server-python/search-apps.md - `search_flows` — Read — https://policylayer.com/tools/kestra-io-mcp-server-python/search-flows.md - `search_logs` — Read — https://policylayer.com/tools/kestra-io-mcp-server-python/search-logs.md - …and 8 more: https://policylayer.com/tools/kestra-io-mcp-server-python.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=kestra-io-mcp-server-python · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/kestra-io-mcp-server-python