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

namespace_directory_action

A other tool on the Kestra Python MCP server.

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

This record as markdown: /tools/kestra-io-mcp-server-python/namespace-directory-action.md

What namespace_directory_action does on Kestra Python MCP Server

AI agents call namespace_directory_action as a supporting operation in Kestra Python MCP Server workflows.

Why namespace_directory_action is rated Low

With no description available, the action type is ambiguous. The word 'action' in the name could imply any category. Given the context of Kestra workflows and sibling tools that include destructive operations, there is moderate risk, but without evidence I cannot assign a specific category. Defaulting to Other with low confidence.

From the tool's definition Tool description is empty and uninformative. Tool name 'namespace_directory_action' suggests some operation on a namespace directory, but the exact action (read, write, delete, execute) cannot be determined from the name alone.

Questions about namespace_directory_action

What does the namespace_directory_action tool do? +

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

How do I enforce a policy on namespace_directory_action? +

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

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

Can I rate-limit namespace_directory_action? +

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

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

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

Across the catalogue

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