remove_course_enrollment

Remove a contact from a course

SERVERGoHighLevel MCP Server SOURCEbusybee3333/go-high-level-mcp-2026-complete
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/busybee3333-go-high-level-mcp-2026-complete/remove-course-enrollment.md

What remove_course_enrollment does on GoHighLevel MCP Server

AI agents call remove_course_enrollment to permanently remove resources in GoHighLevel MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why remove_course_enrollment is rated Critical

Removing a course enrollment strips a contact's access to course content and likely deletes the enrollment record. This is typically irreversible without manual re-enrollment, making it a Destructive action. The blast radius is high because it affects a user's access to paid or assigned educational content.

From the tool's definition 'Remove a contact from a course' — removing enrollment is an irreversible action that revokes access and deletes the enrollment record

Questions about remove_course_enrollment

What does the remove_course_enrollment tool do? +

Remove a contact from a course. It is categorised as a Destructive tool in the GoHighLevel MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_course_enrollment? +

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

remove_course_enrollment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_course_enrollment? +

Yes. Add a rate_limit block to the remove_course_enrollment 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 remove_course_enrollment completely? +

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

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

More on GoHighLevel MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GoHighLevel MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.