update_cards · Codecks MCP: Risk & Policy

WHAT IT DOES

What update_cards does on Codecks

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

WHY IT NEEDS A POLICY

Why update_cards needs a policy

This tool modifies existing card properties reversibly. While 'update' operations can affect project state, they are not irreversible (data can be updated again), do not execute code or trigger external operations, do not move money, and do not delete data. Therefore, it falls under Write rather than Execute or Destructive.

From the tool's definition Tool name 'update_cards' and description 'Update card properties' indicate reversible modification of card data (owner/tags/milestone/deck/title/content/hero).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_cards Rate-limited

update_cards 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": {
    "update_cards": {
      "limits": [
        {
          "counter": "update_cards_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 Codecks, so you can run agents against it safely.

FAQ

Questions about update_cards

What does the update_cards tool do? +

Update card properties. Doc cards: only owner/tags/milestone/deck/title/content/hero. It is categorised as a Write tool in the Codecks MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_cards? +

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

What risk level is update_cards? +

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

Can I rate-limit update_cards? +

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

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

update_cards is provided by the Codecks MCP server (rangogamedev/codecks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.