teamsnap_create_event · TeamSnap MCP Server MCP

WHAT IT DOES

What teamsnap_create_event does on TeamSnap MCP Server

AI agents use teamsnap_create_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_create_event needs a policy

The tool creates new calendar events in a team management system. This is a Write operation because it creates data reversibly (events can be edited or deleted later). Severity is medium because misuse could create unwanted calendar entries affecting team coordination, but the impact is limited to the team's calendar and does not involve financial transactions, data destruction, or code execution.

From the tool's definition Tool name contains 'create' and description states 'Create a new event (game, practice, meeting)'. This is a reversible modification that adds data to the TeamSnap system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

teamsnap_create_event Rate-limited

teamsnap_create_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_create_event": {
      "limits": [
        {
          "counter": "teamsnap_create_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_create_event

What does the teamsnap_create_event tool do? +

Create a new event (game, practice, meeting). Returns the created event with localized times. 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_create_event? +

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

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

Can I rate-limit teamsnap_create_event? +

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

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

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