Get recent run history across all scenarios/recipes
AI agents call get_recent_runs 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 queries and retrieves historical execution logs/run data from Dataiku DSS scenarios and recipes. It performs a read-only lookup operation without creating, modifying, deleting, or executing any workflows. The action is non-destructive and has no side effects beyond returning information to the caller.
From the tool's definition Tool name 'get_recent_runs' and description 'Get recent run history across all scenarios/recipes' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get recent run history across all scenarios/recipes. 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_recent_runs: 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_recent_runs 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_recent_runs 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_recent_runs. 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_recent_runs 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 →