List available Python/R environments
AI agents call get_code_environments to retrieve information from Dataiku DSS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read/list operation that simply enumerates available code environments. The blast radius of misuse is minimal—an agent could learn what environments exist but cannot modify or execute code within them. No data destruction, financial impact, or code execution occurs.
From the tool's definition Tool name 'get_code_environments' with description 'List available Python/R environments' performs a retrieval operation with no side effects. It queries and returns information about existing environments without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
List available Python/R environments. It is categorised as a Read tool in the Dataiku DSS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dataiku DSS MCP Server MCP server in PolicyLayer and add a rule for get_code_environments: 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 Dataiku DSS MCP Server. Nothing to install.
get_code_environments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_code_environments 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 get_code_environments. 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.
get_code_environments is provided by the Dataiku DSS MCP Server MCP server (steven0lisa/mcp-dataiku). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →