google_ads_metrics_get_google_ads_campaign_window
GetGoogleAdsCampaignWindow aggregates each campaign over an arbitrary date range — the shape a charge is reconciled against. Distinct from the monthly list above, whose month key cannot describe a billing period that starts mid-month.
This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/google-ads-metrics-get-google-ads-campaign-window.md
What google_ads_metrics_get_google_ads_campaign_window does on Lovie Company Formation MCP
AI agents call google_ads_metrics_get_google_ads_campaign_window to retrieve information from Lovie Company Formation MCP 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 |
|---|---|---|---|
companyId | string | — | |
periodEnd | string | — | |
customerId | string | — | |
periodStart | string | — |
Parameters from the server's own tool schema.
Why google_ads_metrics_get_google_ads_campaign_window is rated Low
Even though google_ads_metrics_get_google_ads_campaign_window 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 google_ads_metrics_get_google_ads_campaign_window safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Lovie Company Formation MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For google_ads_metrics_get_google_ads_campaign_window, this is the rule to start with:
google_ads_metrics_get_google_ads_campaign_window 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 Lovie Company Formation MCP, apply this rule, and every google_ads_metrics_get_google_ads_campaign_window call is checked against it from then on.
Questions about google_ads_metrics_get_google_ads_campaign_window
GetGoogleAdsCampaignWindow aggregates each campaign over an arbitrary date range — the shape a charge is reconciled against. Distinct from the monthly list above, whose month key cannot describe a billing period that starts mid-month. It is categorised as a Read tool in the Lovie Company Formation MCP MCP Server, which means it retrieves data without modifying state.
google_ads_metrics_get_google_ads_campaign_window accepts 4 parameters: companyId, periodEnd, customerId, periodStart. The full parameter table on this page comes from the server's own tool schema.
Register the Lovie Company Formation MCP server in PolicyLayer and add a rule for google_ads_metrics_get_google_ads_campaign_window: 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 Lovie Company Formation MCP. Nothing to install.
google_ads_metrics_get_google_ads_campaign_window 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 google_ads_metrics_get_google_ads_campaign_window 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 google_ads_metrics_get_google_ads_campaign_window. 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.
google_ads_metrics_get_google_ads_campaign_window is provided by the Lovie Company Formation MCP server (lovie). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Lovie Company Formation, and thousands of servers like it.
This server
Across the catalogue