Post an in-app message to the team
AI agents use teamsnap_send_team_message 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.
This tool creates and sends a message to a team, which is a reversible write operation. The blast radius is medium because misconfigured messages could spam team members or send unintended communications, potentially disrupting team operations or damaging relationships, but the action is not destructive, executable code, or financial in nature.
From the tool's definition Tool name contains 'send' and description states 'Post an in-app message to the team', indicating creation of new message data within TeamSnap.
Attacks that exploit this kind of access
Post an in-app message to 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.
Register the TeamSnap MCP Server MCP server in PolicyLayer and add a rule for teamsnap_send_team_message: 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.
teamsnap_send_team_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the teamsnap_send_team_message 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.
Set action: deny in the PolicyLayer policy for teamsnap_send_team_message. 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.
teamsnap_send_team_message 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →