Medium Risk

restore_note

Restore a deleted top-level GHL note.

How to control restore_note ↓

AI agents use restore_note to create or update resources in GoHighLevel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GoHighLevel MCP Server environment.

Medium Risk

This tool reverses a destructive action (deletion) and restores data to an accessible state. While it recovers deleted information rather than permanently destroying it, it modifies system state irreversibly in the sense that the note's deleted status changes to restored. It is categorized as Write rather than Destructive because the operation creates/restores accessible data rather than permanently destroying it.

From the tool's definition Tool description: 'Restore a deleted top-level GHL note.' The action restores (reverses deletion of) a note, modifying state by making previously deleted data accessible again.

Documented attack patterns abuse exactly the kind of access restore_note 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 restore_note:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "restore_note": {
      "limits": [
        {
          "counter": "restore_note_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

restore_note 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.

  1. Create a free account and register GoHighLevel MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the restore_note tool do? +

Restore a deleted top-level GHL note. It is categorised as a Write tool in the GoHighLevel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on restore_note? +

Register the GoHighLevel MCP Server MCP server in PolicyLayer and add a rule for restore_note: 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.

What risk level is restore_note? +

restore_note is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit restore_note? +

Yes. Add a rate_limit block to the restore_note 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.

How do I block restore_note completely? +

Set action: deny in the PolicyLayer policy for restore_note. 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.

What MCP server provides restore_note? +

restore_note 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.

Enforce policy on every GoHighLevel MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.