move_column · Basecamp MCP Server MCP: Risk & Policy

WHAT IT DOES

What move_column does on Basecamp MCP Server

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

WHY IT NEEDS A POLICY

Why move_column needs a policy

This tool modifies the structure/organization of data (column position) but does not create, delete, or execute arbitrary code. It is reversible and has minimal blast radius. It is classified as Write rather than Execute because it performs a straightforward data modification, not a conditional or complex operation whose effects depend heavily on runtime context.

From the tool's definition Tool name 'move_column' and description 'Move a column to a new position' indicate a reversible modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_column Rate-limited

move_column 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": {
    "move_column": {
      "limits": [
        {
          "counter": "move_column_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 Basecamp MCP Server, so you can run agents against it safely.

FAQ

Questions about move_column

What does the move_column tool do? +

Move a column to a new position. It is categorised as a Write tool in the Basecamp 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 move_column? +

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

What risk level is move_column? +

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

Can I rate-limit move_column? +

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

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

move_column is provided by the Basecamp MCP Server MCP server (jhliberty/basecamp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

move_column is one line of Basecamp MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →