batch_update_objects · Dataiku DSS MCP Server MCP

WHAT IT DOES

What batch_update_objects does on Dataiku DSS MCP Server

AI agents use batch_update_objects to create or update resources in Dataiku DSS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dataiku DSS MCP Server environment.

WHY IT NEEDS A POLICY

Why batch_update_objects needs a policy

This is a Write operation because it modifies data reversibly (updates, not deletes). Severity is high rather than medium due to the batch nature of the operation—a single AI agent invocation could affect many objects simultaneously, creating significant unintended consequences across data pipelines and workflows.

From the tool's definition Tool name 'batch_update_objects' and description 'Update multiple objects with similar changes' indicate bulk modification capability.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_update_objects Rate-limited

batch_update_objects stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "batch_update_objects": {
      "limits": [
        {
          "counter": "batch_update_objects_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Dataiku DSS MCP Server, so you can run agents against it safely.

FAQ

Questions about batch_update_objects

What does the batch_update_objects tool do? +

Update multiple objects with similar changes. It is categorised as a Write tool in the Dataiku DSS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on batch_update_objects? +

Register the Dataiku DSS MCP Server MCP server in PolicyLayer and add a rule for batch_update_objects: 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.

What risk level is batch_update_objects? +

batch_update_objects is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit batch_update_objects? +

Yes. Add a rate_limit block to the batch_update_objects 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.

How do I block batch_update_objects completely? +

Set action: deny in the PolicyLayer policy for batch_update_objects. 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.

What MCP server provides batch_update_objects? +

batch_update_objects 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.