change_column_type · DataBeak MCP: Risk & Policy

WHAT IT DOES

What change_column_type does on DataBeak

AI agents use change_column_type 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 change_column_type needs a policy

Changing column types modifies data representation reversibly (can be undone by changing back), making this a Write operation. It affects data structure but not deletion or irreversible loss. Severity is medium because incorrect type conversions could corrupt data integrity or break downstream processing, though the operation is theoretically reversible.

From the tool's definition Tool name is 'change_column_type' which indicates modifying column data types in a dataset. The empty description limits certainty, but the name clearly suggests altering schema/structure of CSV data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

change_column_type Rate-limited

change_column_type 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": {
    "change_column_type": {
      "limits": [
        {
          "counter": "change_column_type_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 change_column_type

What does the change_column_type tool do? +

change_column_type. 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 change_column_type? +

Register the DataBeak MCP server in PolicyLayer and add a rule for change_column_type: 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 change_column_type? +

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

Can I rate-limit change_column_type? +

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

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

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