snapshots_create_snapshot_share_link
Create Snapshot Share Link (requires an agency-level token, not a location PIT)
This record as markdown: /tools/aiwerk-mcp-server-ghl/snapshots-create-snapshot-share-link.md
What snapshots_create_snapshot_share_link does on Ghl
AI agents use snapshots_create_snapshot_share_link to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
companyId | string | Yes | |
share_type | string | Yes | Type of share link to generate |
snapshot_id | string | Yes | id for snapshot to be shared |
share_location_id | string | — | Comma separated Sub-Account ids to create sub-account restricted share link |
relationship_number | string | — | Comma separated Relationship number of Agencies to create agency restricted share link |
Parameters from the server's own tool schema.
Why snapshots_create_snapshot_share_link is rated Medium
An AI agent can call snapshots_create_snapshot_share_link faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs snapshots_create_snapshot_share_link safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snapshots_create_snapshot_share_link, this is the rule to start with:
snapshots_create_snapshot_share_link 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 Ghl, apply this rule, and every snapshots_create_snapshot_share_link call is checked against it from then on.
Questions about snapshots_create_snapshot_share_link
Create Snapshot Share Link (requires an agency-level token, not a location PIT). It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
snapshots_create_snapshot_share_link accepts 5 parameters: companyId, share_type, snapshot_id, share_location_id, relationship_number. Required: companyId, share_type, snapshot_id. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for snapshots_create_snapshot_share_link: 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 Ghl. Nothing to install.
snapshots_create_snapshot_share_link 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 snapshots_create_snapshot_share_link 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 snapshots_create_snapshot_share_link. 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.
snapshots_create_snapshot_share_link is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue