complete_checklist_item · Things Cloud MCP: Risk & Policy

WHAT IT DOES

What complete_checklist_item does on Things Cloud MCP

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

WHY IT NEEDS A POLICY

Why complete_checklist_item needs a policy

This tool updates the completion status of a checklist item within a task, which constitutes a modification of data. The action is reversible (an item can be unchecked), making it a Write operation rather than Destructive. The severity is low because the impact is limited to a single task's checklist state with minimal blast radius if invoked incorrectly.

From the tool's definition Tool name is 'complete_checklist_item' with description 'Check off a checklist item.' This modifies task state by marking a checklist item as complete, which is a reversible change.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

complete_checklist_item Rate-limited

complete_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": {
    "complete_checklist_item": {
      "limits": [
        {
          "counter": "complete_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 Things Cloud MCP, so you can run agents against it safely.

FAQ

Questions about complete_checklist_item

What does the complete_checklist_item tool do? +

Check off a checklist item. It is categorised as a Write tool in the Things Cloud MCP 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_checklist_item? +

Register the Things Cloud MCP server in PolicyLayer and add a rule for complete_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 Things Cloud MCP. Nothing to install.

What risk level is complete_checklist_item? +

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

Can I rate-limit complete_checklist_item? +

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

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

complete_checklist_item is provided by the Things Cloud MCP server (nkootstra/things). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.