create_card_step · Basecamp MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_card_step does on Basecamp MCP Server

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

This tool creates a new sub-task within a card in Basecamp, which is a write operation that modifies project management data. The impact is limited to creating a single organizational element without destructive consequences, financial implications, or code execution. The scope is confined to a specific card's workflow, making it low severity.

From the tool's definition Tool name 'create_card_step' and description 'Create a new step (sub-task) for a card' indicate data creation/modification operation. The action is reversible (steps can be deleted or modified).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_card_step Rate-limited

create_card_step 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_step": {
      "limits": [
        {
          "counter": "create_card_step_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_step

What does the create_card_step tool do? +

Create a new step (sub-task) for a card. 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_step? +

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

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

Can I rate-limit create_card_step? +

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

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

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