complete_card_step · Basecamp MCP Server MCP: Risk & Policy

WHAT IT DOES

What complete_card_step does on Basecamp MCP Server

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

This tool creates or modifies data (the completion status of a card step) in a reversible manner. It does not execute arbitrary code, delete data permanently, or involve financial transactions. While it changes state in Basecamp, the action can be undone by unmarking the step as complete, fitting the Write category.

From the tool's definition Tool name is 'complete_card_step' with description 'Mark a card step as complete'. This modifies the state of a card step by marking it as complete, which is a reversible status change.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

complete_card_step Rate-limited

complete_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": {
    "complete_card_step": {
      "limits": [
        {
          "counter": "complete_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 complete_card_step

What does the complete_card_step tool do? +

Mark a card step as complete. 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 complete_card_step? +

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

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

Can I rate-limit complete_card_step? +

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

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

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