Get custom-field values defined by the team or league (e.g. waiver status, allergies, emergency contact). Provide exactly one of team_id or member_id.
AI agents call teamsnap_get_custom_data to retrieve information from TeamSnap MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation as it only retrieves existing data with no side effects. However, severity is elevated to 'medium' rather than 'low' because the tool accesses sensitive personal information (allergies, emergency contact details, waiver status) that could be misused if an agent makes unauthorized queries. The blast radius depends on team_id/member_id access control on the TeamSnap backend.
From the tool's definition Tool name contains 'get_' and description states 'Get custom-field values'. It retrieves data without modification. However, the custom-field values retrieved (waiver status, allergies, emergency contact) constitute sensitive personal/health information.
Attacks that exploit this kind of access
Get custom-field values defined by the team or league (e.g. waiver status, allergies, emergency contact). Provide exactly one of team_id or member_id. It is categorised as a Read tool in the TeamSnap MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TeamSnap MCP Server MCP server in PolicyLayer and add a rule for teamsnap_get_custom_data: 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_get_custom_data is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the teamsnap_get_custom_data 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_get_custom_data. 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_get_custom_data 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 →