Get detailed run logs and error messages for failed scenarios
AI agents call get_scenario_logs 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 and queries existing log data from completed scenario runs. It has no side effects—it does not modify, delete, execute, or trigger any operations. The word 'Get' combined with 'logs' and 'messages' confirms this is a pure read operation. Low severity because log retrieval poses minimal risk unless logs contain sensitive credentials, but the tool itself is non-destructive and non-actionable.
From the tool's definition Tool name 'get_scenario_logs' and description 'Get detailed run logs and error messages for failed scenarios' indicate retrieval of historical log data with no modification or execution of scenarios.
Attacks that exploit this kind of access
Get detailed run logs and error messages for failed scenarios. 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_logs: 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_logs 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_logs 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_logs. 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_logs 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 →