create_card · Basecamp MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_card does on Basecamp MCP Server

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

This tool creates a new card, which is a reversible write operation that adds data to a Basecamp project management system. It does not execute arbitrary code, delete data, or commit financial transactions. The severity is medium because misuse could create unwanted cards or spam the project, but the impact is contained to task management metadata and can be undone by deletion.

From the tool's definition Tool name is 'create_card' and description states 'Create a new card in a column' — this creates new data in Basecamp.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_card Rate-limited

create_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": {
    "create_card": {
      "limits": [
        {
          "counter": "create_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 create_card

What does the create_card tool do? +

Create a new card in a 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 create_card? +

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

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

Can I rate-limit create_card? +

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

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

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

// THE FULL RECORD

create_card 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 →