code_env

Code env ops: list/get. get returns package summaries; set full=true for full package lists.

Part of the Dataiku MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

dataiku-mcp Write Risk 2/5

// WHEN AI AGENTS USE THIS TOOL

AI agents use code_env to create or modify resources in Dataiku MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON CODE_ENV

Without a policy, an AI agent could call code_env repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Dataiku MCP.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

dataiku-mcp.yaml

tools:
  code_env:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Dataiku MCP policy for all 9 tools.

// DETAILS

Tool Name code_env

Category Write

MCP Server Dataiku MCP MCP Server

Risk Level Medium

// MORE DATAIKU MCP TOOLS

Destructive dataset Destructive recipe Destructive scenario Execute job Write managed_folder Write variable Other connection Read project

View all 9 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like code_env have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the code_env tool do? +

Code env ops: list/get. get returns package summaries; set full=true for full package lists.. It is categorised as a Write tool in the Dataiku MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on code_env? +

Add a rule in your Intercept YAML policy under the tools section for code_env. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Dataiku MCP MCP server.

What risk level is code_env? +

code_env is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit code_env? +

Yes. Add a rate_limit block to the code_env rule in your Intercept 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 code_env completely? +

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

code_env is provided by the Dataiku MCP MCP server (dataiku-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

code_env

Enforce policies on Dataiku MCP