Get step configuration including Python code
AI agents call get_scenario_steps 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 tool retrieves scenario step configuration and associated Python code for inspection and review purposes. The verb 'Get' and the absence of language suggesting modification, deletion, or execution (run/execute/trigger) clearly places it in the Read category. The information retrieved (step configuration, code snippets) could be sensitive but reading it does not cause side effects or irreversible changes.
From the tool's definition Tool name 'get_scenario_steps' with description 'Get step configuration including Python code' indicates retrieval of existing configuration data without modification or execution.
Attacks that exploit this kind of access
Get step configuration including Python code. 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_scenario_steps: 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_scenario_steps 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_scenario_steps 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_scenario_steps. 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_scenario_steps 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 →