This record as markdown: /tools/ghl/get-location-templates.md
What get_location_templates does on Ghl
AI agents call get_location_templates to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
skip | number | — | Number to skip for pagination (default: 0) |
type | string | — | Filter by template type |
limit | number | — | Maximum number to return (default: 25) |
deleted | boolean | — | Include deleted templates (default: false) |
originId | string | Yes | Origin ID (required parameter) |
locationId | string | Yes | The location ID |
Parameters from the server's own tool schema.
Why get_location_templates is rated Low
This tool retrieves existing SMS/Email templates associated with a location. The verb 'Get' and the lack of any language suggesting mutation, deletion, or execution of operations confirm this is a Read operation. The data retrieved (templates) is informational only and carries minimal risk if exposed to an AI agent, as it cannot cause side effects beyond accessing stored template content.
From the tool's definition Tool name 'get_location_templates' and description 'Get SMS/Email templates for a location' indicate a retrieval operation with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
The rule that runs get_location_templates 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 get_location_templates, this is the rule to start with:
get_location_templates is read-only, so it stays allowed. 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 get_location_templates call is checked against it from then on.
Questions about get_location_templates
Get SMS/Email templates for a location. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_location_templates accepts 6 parameters: skip, type, limit, deleted, originId, locationId. Required: originId, locationId. 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 get_location_templates: 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.
get_location_templates 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_location_templates 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_location_templates. 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_location_templates is provided by the Ghl MCP server (ghl-mcp-server). 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