teamsnap_set_availability · TeamSnap MCP Server MCP

WHAT IT DOES

What teamsnap_set_availability does on TeamSnap MCP Server

AI agents use teamsnap_set_availability 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_set_availability needs a policy

This tool modifies availability status for team members, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money, placing it in the Write category. Severity is medium because incorrect availability changes could cause scheduling confusion, missed events, or team coordination failures, but the impact is limited in scope and the operation is reversible.

From the tool's definition Tool name 'teamsnap_set_availability' combined with context that it 'Set[s] a member' indicates modification of availability data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

teamsnap_set_availability Rate-limited

teamsnap_set_availability 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_set_availability": {
      "limits": [
        {
          "counter": "teamsnap_set_availability_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_set_availability

What does the teamsnap_set_availability tool do? +

Set a member. 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_set_availability? +

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

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

Can I rate-limit teamsnap_set_availability? +

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

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

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