namespace_file_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-file-action.md

WHAT IT DOES

What namespace_file_action does on Kestra Python MCP Server

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

RISK

Why namespace_file_action is rated Low

The description is empty, so the exact behavior cannot be determined from available information. The name 'namespace_file_action' suggests file operations within a namespace, which could range from Read to Destructive depending on the action parameter. Given the ambiguity, I assign 'Other' with low confidence, but note that misuse could have medium severity if it allows file deletion or overwriting.

From the tool's definition Tool name is 'namespace_file_action' and description is empty or uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

namespace_file_action Rate-limited

namespace_file_action gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "namespace_file_action": {
      "limits": [
        {
          "counter": "namespace_file_action_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR 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 namespace_file_action call is checked against it from then on.

FAQ

Questions about namespace_file_action

What does the namespace_file_action tool do? +

namespace_file_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_file_action? +

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

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

Can I rate-limit namespace_file_action? +

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

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

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

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

file_synthesis on Agent Store → The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →