This record as markdown: /tools/aiwerk-mcp-server-ghl/ad-manager-fb-get-reporting.md
What ad_manager_fb_get_reporting does on Ghl
AI agents call ad_manager_fb_get_reporting 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 |
|---|---|---|---|
type | string | Yes | Integration source type |
fields | array | Yes | Comma-separated reporting fields |
endDate | string | Yes | Report end date |
groupBy | string | Yes | Time grouping interval |
startDate | string | Yes | Report start date |
locationId | string | — | Location identifier Defaults to GHL_LOCATION_ID when omitted. |
Parameters from the server's own tool schema.
Why ad_manager_fb_get_reporting is rated Low
Even though ad_manager_fb_get_reporting only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs ad_manager_fb_get_reporting 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 ad_manager_fb_get_reporting, this is the rule to start with:
ad_manager_fb_get_reporting 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 ad_manager_fb_get_reporting call is checked against it from then on.
Questions about ad_manager_fb_get_reporting
Get reporting data. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
ad_manager_fb_get_reporting accepts 6 parameters: type, fields, endDate, groupBy, startDate, locationId. Required: type, fields, endDate, groupBy, startDate. 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 ad_manager_fb_get_reporting: 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.
ad_manager_fb_get_reporting 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 ad_manager_fb_get_reporting 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 ad_manager_fb_get_reporting. 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.
ad_manager_fb_get_reporting is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). 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