audit_location_ads_setup

Read-only audit of location setup relevant to paid-ad lead routing, forms, workflows, calendars, tags, and email follow-up.

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

This record as markdown: /tools/busybee3333-go-high-level-mcp-2026-complete/audit-location-ads-setup.md

What audit_location_ads_setup does on GoHighLevel MCP Server

AI agents call audit_location_ads_setup to retrieve information from GoHighLevel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why audit_location_ads_setup is rated Low

The tool explicitly states it is 'read-only' and performs an audit, meaning it only retrieves and inspects configuration data without making any modifications or triggering side effects.

From the tool's definition Read-only audit of location setup relevant to paid-ad lead routing, forms, workflows, calendars, tags, and email follow-up.

Questions about audit_location_ads_setup

What does the audit_location_ads_setup tool do? +

Read-only audit of location setup relevant to paid-ad lead routing, forms, workflows, calendars, tags, and email follow-up. It is categorised as a Read tool in the GoHighLevel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on audit_location_ads_setup? +

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

audit_location_ads_setup is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit audit_location_ads_setup? +

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

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

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

Across the catalogue

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