add_checklist_item · Framedeck MCP: Risk & Policy

WHAT IT DOES

What add_checklist_item does on Framedeck

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

WHY IT NEEDS A POLICY

Why add_checklist_item needs a policy

Adding a checklist item to a card creates or appends data to an existing card in the Framedeck Kanban system. This is a reversible write operation — the item can be removed or modified later. It does not execute arbitrary code, delete data irreversibly, move money, or cause external side effects beyond updating the card's checklist state. The blast radius of misuse is limited to polluting a single card's task list.

From the tool's definition Tool description states 'Add a subtask/checklist item to a card' — the verb 'Add' indicates creation of new data (a checklist item). This is a write operation that modifies card content reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_checklist_item Rate-limited

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

FAQ

Questions about add_checklist_item

What does the add_checklist_item tool do? +

Add a subtask/checklist item to a card. It is categorised as a Write tool in the Framedeck MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_checklist_item? +

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

What risk level is add_checklist_item? +

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

Can I rate-limit add_checklist_item? +

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

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

add_checklist_item is provided by the Framedeck MCP server (lukaris/framedeck-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.