move_card · Basecamp MCP Server MCP: Risk & Policy

WHAT IT DOES

What move_card does on Basecamp MCP Server

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

Moving a card changes its column assignment in a Basecamp project, which is a data modification. This is reversible (cards can be moved again), so it qualifies as Write rather than Destructive. The severity is medium because it affects project organization and could cause confusion if misused, but the change is easily undone and doesn't involve deletion, code execution, or financial impact.

From the tool's definition Tool performs 'Move a card to a new column' - this modifies the state and position of data (card location) within Basecamp, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_card Rate-limited

move_card 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_card": {
      "limits": [
        {
          "counter": "move_card_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_card

What does the move_card tool do? +

Move a card to a new column. 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_card? +

Register the Basecamp MCP Server MCP server in PolicyLayer and add a rule for move_card: 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_card? +

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

Can I rate-limit move_card? +

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

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

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