Build a dataset
AI agents invoke build_dataset to trigger actions in Dataiku DSS MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Building a dataset executes code/transformations as defined in Dataiku recipes and scenarios. While not immediately destructive (the dataset still exists after), it triggers external computational operations that can have broad side effects: consuming computational resources, modifying derived datasets, triggering downstream jobs, and potentially failing or corrupting data if the pipeline has issues.
From the tool's definition Tool name 'build_dataset' combined with 'Build a dataset' description indicates triggering a computation/pipeline execution.
Attacks that exploit this kind of access
Build a dataset. It is categorised as a Execute tool in the Dataiku DSS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Dataiku DSS MCP Server MCP server in PolicyLayer and add a rule for build_dataset: 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.
build_dataset is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the build_dataset 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 build_dataset. 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.
build_dataset 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 →