codecks_move_card · Codecks MCP Server MCP: Risk & Policy

WHAT IT DOES

What codecks_move_card does on Codecks MCP Server

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

WHY IT NEEDS A POLICY

Why codecks_move_card needs a policy

Moving a card between decks is a write operation that modifies card metadata/relationships within Codecks. It is reversible (card can be moved back), so it does not qualify as Destructive. The severity is medium because misuse could disorganize project workflows and create confusion, but the blast radius is contained to task organization within a single project system rather than system-wide or financial impacts.

From the tool's definition Tool performs 'Move a card to a different deck' — modifies card state and organization by changing its location within the project management system. This is a reversible operation that alters data structure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

codecks_move_card Rate-limited

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

FAQ

Questions about codecks_move_card

What does the codecks_move_card tool do? +

Move a card to a different deck. It is categorised as a Write tool in the Codecks 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 codecks_move_card? +

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

What risk level is codecks_move_card? +

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

Can I rate-limit codecks_move_card? +

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

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

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