run_custom_report · Google Ad Manager MCP Server MCP

WHAT IT DOES

What run_custom_report does on Google Ad Manager MCP Server

AI agents invoke run_custom_report to trigger actions in Google Ad Manager MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

THE RISK

High Risk

Why run_custom_report needs a policy

The name 'run_custom_report' implies executing a reporting operation in Google Ad Manager. In ad platforms, running a custom report typically triggers a query/execution against ad data (Execute category), potentially with significant blast radius if it exposes sensitive campaign or financial data. However, since the description is empty, confidence is reduced.

From the tool's definition Tool name 'run_custom_report' — description is empty and uninformative.

Documented attack patterns abuse exactly the kind of access run_custom_report gives an agent:

POLICY

How to control run_custom_report

PolicyLayer is an MCP gateway — it sits between your AI agents and Google Ad Manager MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_custom_report:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_custom_report": {
      "limits": [
        {
          "counter": "run_custom_report_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

run_custom_report stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Google Ad Manager MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Google Ad Manager MCP Server tools

Execute run_inventory_report run_inventory_report Write associate_creative_with_line_item associate_creative_with_line_item Write duplicate_line_item duplicate_line_item Write find_or_create_advertiser find_or_create_advertiser Write find_or_create_order find_or_create_order Write pause_line_item pause_line_item Write approve_line_item approve_line_item Write archive_line_item archive_line_item

All 35 Google Ad Manager MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Google Ad Manager MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about run_custom_report

What does the run_custom_report tool do? +

run_custom_report. It is categorised as a Execute tool in the Google Ad Manager MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_custom_report? +

Register the Google Ad Manager MCP Server MCP server in PolicyLayer and add a rule for run_custom_report: 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 Google Ad Manager MCP Server. Nothing to install.

What risk level is run_custom_report? +

run_custom_report is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_custom_report? +

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

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

run_custom_report is provided by the Google Ad Manager MCP Server MCP server (matiouscorp/google-ad-manager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Google Ad Manager MCP Server tool call.

Start from Google Ad Manager MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

35 Google Ad Manager MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.