teamsnap_update_event · TeamSnap MCP Server MCP

WHAT IT DOES

What teamsnap_update_event does on TeamSnap MCP Server

AI agents use teamsnap_update_event 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_event needs a policy

teamsnap_update_event modifies existing events in a reversible manner—updates can be undone by subsequent updates. While the is_canceled field has team-wide notification side effects, it remains reversible (events can be un-canceled).

From the tool's definition Tool description states it 'Update[s] an existing event' with 'Non-destructive fields' that 'update freely', and includes special handling for is_canceled which 'notifies the team' when set to true.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

teamsnap_update_event Rate-limited

teamsnap_update_event 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_event": {
      "limits": [
        {
          "counter": "teamsnap_update_event_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_event

What does the teamsnap_update_event tool do? +

Update an existing event via a patch object. Non-destructive fields (name, start_date, location_id, duration_in_minutes, notes, uniform, opponent_id, minutes_to_arrive_early) update freely. Setting is_canceled: true requires confirm: true because it notifies the team. 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_event? +

Register the TeamSnap MCP Server MCP server in PolicyLayer and add a rule for teamsnap_update_event: 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_event? +

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

Can I rate-limit teamsnap_update_event? +

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

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

teamsnap_update_event 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.