fill_column_nulls · DataBeak MCP: Risk & Policy

WHAT IT DOES

What fill_column_nulls does on DataBeak

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

WHY IT NEEDS A POLICY

Why fill_column_nulls needs a policy

This tool creates or modifies data reversibly by populating null values in a column, which is a Write operation. It does not execute code, delete data irreversibly, or move money. Severity is medium because misuse could corrupt data analysis pipelines, but changes are typically reversible by reloading the source data or undoing the fill operation.

From the tool's definition Tool name 'fill_column_nulls' indicates modification of data by filling null/missing values. Sibling tools include 'fill_missing_values' and 'change_column_type' which are clearly write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fill_column_nulls Rate-limited

fill_column_nulls 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": {
    "fill_column_nulls": {
      "limits": [
        {
          "counter": "fill_column_nulls_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 DataBeak, so you can run agents against it safely.

FAQ

Questions about fill_column_nulls

What does the fill_column_nulls tool do? +

fill_column_nulls. It is categorised as a Write tool in the DataBeak MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on fill_column_nulls? +

Register the DataBeak MCP server in PolicyLayer and add a rule for fill_column_nulls: 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 DataBeak. Nothing to install.

What risk level is fill_column_nulls? +

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

Can I rate-limit fill_column_nulls? +

Yes. Add a rate_limit block to the fill_column_nulls 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 fill_column_nulls completely? +

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

fill_column_nulls is provided by the DataBeak MCP server (jonpspri/databeak). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.