growsurf_troubleshoot_referral_tracking
Diagnose referral tracking and program problems. Accepts a symptom or description without requiring a program or participant ID. Covers referrals not credited, participant emails not sending, rewards not issued, participants not added, Universal Code not detected, integrations or CRMs not syncing...
This record as markdown: /tools/com-growsurf-growsurf/growsurf-troubleshoot-referral-tracking.md
What growsurf_troubleshoot_referral_tracking does on GrowSurf
AI agents call growsurf_troubleshoot_referral_tracking to retrieve information from GrowSurf without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why growsurf_troubleshoot_referral_tracking is rated Low
Even though growsurf_troubleshoot_referral_tracking only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs growsurf_troubleshoot_referral_tracking safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GrowSurf, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For growsurf_troubleshoot_referral_tracking, this is the rule to start with:
growsurf_troubleshoot_referral_tracking is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GrowSurf, apply this rule, and every growsurf_troubleshoot_referral_tracking call is checked against it from then on.
Questions about growsurf_troubleshoot_referral_tracking
Diagnose referral tracking and program problems. Accepts a symptom or description without requiring a program or participant ID. Covers referrals not credited, participant emails not sending, rewards not issued, participants not added, Universal Code not detected, integrations or CRMs not syncing, Zapier errors, fraud flags, and analytics discrepancies. Returns ordered diagnostic checks, likely causes, fixes, and documentation links. It does not read program or participant records. Unknown. It is categorised as a Read tool in the GrowSurf MCP Server, which means it retrieves data without modifying state.
Register the GrowSurf MCP server in PolicyLayer and add a rule for growsurf_troubleshoot_referral_tracking: 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 GrowSurf. Nothing to install.
growsurf_troubleshoot_referral_tracking 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 growsurf_troubleshoot_referral_tracking 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 growsurf_troubleshoot_referral_tracking. 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.
growsurf_troubleshoot_referral_tracking is provided by the GrowSurf MCP server (@growsurfteam/growsurf-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GrowSurf, and thousands of servers like it.
This server
Across the catalogue