AI agents call namespace_directory_action as a supporting operation in Kestra Python MCP Server workflows.
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.
Documented attack patterns abuse exactly the kind of access namespace_directory_action gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kestra Python MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for namespace_directory_action:
{
"version": "1",
"default": "deny",
"tools": {
"namespace_directory_action": {
"limits": [
{
"counter": "namespace_directory_action_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}namespace_directory_action gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
namespace_directory_action. It is categorised as a Other tool in the Kestra Python MCP Server MCP Server, which means it performs auxiliary operations.
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.
namespace_directory_action is a Other tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
Start from Kestra Python MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 Kestra Python MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.