growsurf_capture_referral_flow_screenshots
Capture temporary GrowSurf preview screenshots after the user explicitly asks for screenshots or screenshot proof. Returns short-lived URLs for the controlled referrer Window and referred-friend experience for this program. This does not prove the user
This record as markdown: /tools/com-growsurf-growsurf/growsurf-capture-referral-flow-screenshots.md
What growsurf_capture_referral_flow_screenshots does on GrowSurf
AI agents use growsurf_capture_referral_flow_screenshots to create or update resources in GrowSurf, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GrowSurf environment.
Why growsurf_capture_referral_flow_screenshots is rated Medium
An AI agent can call growsurf_capture_referral_flow_screenshots faster than any human can review: one bad instruction and it creates or modifies resources in GrowSurf by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs growsurf_capture_referral_flow_screenshots 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_capture_referral_flow_screenshots, this is the rule to start with:
growsurf_capture_referral_flow_screenshots 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.
The button opens the PolicyLayer dashboard: create your workspace, connect GrowSurf, apply this rule, and every growsurf_capture_referral_flow_screenshots call is checked against it from then on.
Questions about growsurf_capture_referral_flow_screenshots
Capture temporary GrowSurf preview screenshots after the user explicitly asks for screenshots or screenshot proof. Returns short-lived URLs for the controlled referrer Window and referred-friend experience for this program. This does not prove the user. It is categorised as a Write tool in the GrowSurf MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GrowSurf MCP server in PolicyLayer and add a rule for growsurf_capture_referral_flow_screenshots: 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_capture_referral_flow_screenshots 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 growsurf_capture_referral_flow_screenshots 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_capture_referral_flow_screenshots. 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_capture_referral_flow_screenshots 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