search_apps

A read tool on the Kestra Python MCP server.

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

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kestra-io-mcp-server-python/search-apps.md

WHAT IT DOES

What search_apps does on Kestra Python MCP Server

AI agents call search_apps to retrieve information from Kestra Python MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why search_apps is rated Low

The tool name strongly suggests a read-only search or query operation typical of listing or discovering applications/flows within the Kestra platform. Without evidence of side effects (create, modify, delete, or execute), and given the sibling tools on this server include destructive operations (delete_*) and execution operations (execute_flow, backfill_executions) that are clearly distinguished by their names,…

From the tool's definition Tool name 'search_apps' suggests a query/search operation that retrieves application data. The description is empty, which limits certainty, but the verb 'search' and naming pattern align with retrieval operations in the context of a Kestra workflow…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_apps 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 search_apps, this is the rule to start with:

search_apps Allowed

search_apps is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_apps": {}
  }
}

ALLOW ONLY 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 search_apps call is checked against it from then on.

FAQ

Questions about search_apps

What does the search_apps tool do? +

search_apps is a read tool on the Kestra Python MCP Server MCP server. It is categorised as a Read tool in the Kestra Python MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_apps? +

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

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

Can I rate-limit search_apps? +

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

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

search_apps 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

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →