teamsnap_update_tracked_item_status

WHAT IT DOES

What teamsnap_update_tracked_item_status does on TeamSnap MCP Server

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

WHY IT NEEDS A POLICY

Why teamsnap_update_tracked_item_status needs a policy

This tool modifies tracked item status records within TeamSnap (snack sign-ups, carpools, etc.) but does not delete data or trigger external financial transactions. Status updates are reversible—items can be changed back to previous states. While it affects team coordination, the scope is limited to status field updates on existing items.

From the tool's definition Tool description states 'Update a tracked-item status' to different states (pending, claimed, or complete), which is a reversible data modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

teamsnap_update_tracked_item_status Rate-limited

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

FAQ

Questions about teamsnap_update_tracked_item_status

What does the teamsnap_update_tracked_item_status tool do? +

Update a tracked-item status (snack sign-up, carpool, etc.) to pending, claimed, or complete. Preview by default. It is categorised as a Write tool in the TeamSnap 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 teamsnap_update_tracked_item_status? +

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

What risk level is teamsnap_update_tracked_item_status? +

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

Can I rate-limit teamsnap_update_tracked_item_status? +

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

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

teamsnap_update_tracked_item_status is provided by the TeamSnap MCP Server MCP server (mrelph/teamsnapmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.