list_namespaces

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/list-namespaces.md

WHAT IT DOES

What list_namespaces does on Kestra Python MCP Server

AI agents call list_namespaces 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 list_namespaces is rated Low

The 'list' prefix strongly signals a read-only query operation that retrieves namespace information without modification. This is consistent with the Read category (search, list, get, fetch). The low severity reflects minimal blast radius—querying available namespaces carries no risk of data loss, financial impact, or unintended execution.

From the tool's definition Tool name 'list_namespaces' indicates a listing/querying operation. The tool sits in a workflow management server alongside flow/execution management tools, and 'list' operations are read-only retrieval of metadata (namespaces).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_namespaces Allowed

list_namespaces 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": {
    "list_namespaces": {}
  }
}

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

FAQ

Questions about list_namespaces

What does the list_namespaces tool do? +

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

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

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

Can I rate-limit list_namespaces? +

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

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

list_namespaces 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

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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