Check the status of a snapshot push operation
AI agents call get_snapshot_push_status to retrieve information from GoHighLevel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about an existing snapshot push operation. It queries data without modifying, deleting, or executing any actions. The operation is read-only with no side effects, blast radius is minimal (information disclosure only), and it poses no risk of unintended state changes or financial impact.
From the tool's definition Tool name 'get_snapshot_push_status' and description 'Check the status of a snapshot push operation' indicate a status query operation with no side effects. The verb 'get' and 'check' are retrieval operations.
Documented attack patterns abuse exactly the kind of access get_snapshot_push_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GoHighLevel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_snapshot_push_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_snapshot_push_status": {}
}
}get_snapshot_push_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check the status of a snapshot push operation. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for get_snapshot_push_status: 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 GoHighLevel MCP Server. Nothing to install.
get_snapshot_push_status 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 get_snapshot_push_status 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 get_snapshot_push_status. 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.
get_snapshot_push_status is provided by the GoHighLevel MCP Server MCP server (busybee3333/go-high-level-mcp-2026-complete). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 566 GoHighLevel MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
566 GoHighLevel MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.