move_kanban_card · Fusebase MCP Server MCP: Risk & Policy

WHAT IT DOES

What move_kanban_card does on Fusebase MCP Server

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

WHY IT NEEDS A POLICY

Why move_kanban_card needs a policy

This is a Write operation because it modifies existing data (a kanban card's column assignment) without deleting data or executing arbitrary code. The change is reversible—cards can be moved back. Severity is medium rather than low because in a workspace context, moving kanban cards could affect task workflows and team visibility, but the blast radius is limited to a single card's organizational state.

From the tool's definition Tool 'move_kanban_card' updates the grouped column of a kanban card, which modifies the card's state/position. The verb 'move' combined with 'updating the grouped column' indicates a reversible modification of data state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_kanban_card Rate-limited

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

FAQ

Questions about move_kanban_card

What does the move_kanban_card tool do? +

Move a kanban card to a different column by updating the grouped column. It is categorised as a Write tool in the Fusebase 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 move_kanban_card? +

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

What risk level is move_kanban_card? +

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

Can I rate-limit move_kanban_card? +

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

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

move_kanban_card is provided by the Fusebase MCP Server MCP server (ryan-haver/fusebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.