run_tracking_diagnostic · KonQuest Meta Ads MCP

WHAT IT DOES

What run_tracking_diagnostic does on KonQuest Meta Ads MCP

AI agents invoke run_tracking_diagnostic to trigger actions in KonQuest Meta Ads MCP. 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.

WHY IT NEEDS A POLICY

Why run_tracking_diagnostic needs a policy

The verb 'run' combined with 'diagnostic' suggests this tool executes an operation (diagnostics) rather than merely reading data. Diagnostics typically involve probing external systems (Meta's tracking infrastructure, pixels on sites as evidenced by sibling tool 'diagnose_pixel_on_site').

From the tool's definition Tool name 'run_tracking_diagnostic' indicates execution of a diagnostic operation. Description is empty, limiting direct evidence. Context shows this is part of a Meta Ads management system with capabilities to modify campaigns and structures.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_tracking_diagnostic Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches KonQuest Meta Ads MCP, so you can run agents against it safely.

FAQ

Questions about run_tracking_diagnostic

What does the run_tracking_diagnostic tool do? +

run_tracking_diagnostic. It is categorised as a Execute tool in the KonQuest Meta Ads MCP 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_tracking_diagnostic? +

Register the KonQuest Meta Ads MCP server in PolicyLayer and add a rule for run_tracking_diagnostic: 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 KonQuest Meta Ads MCP. Nothing to install.

What risk level is run_tracking_diagnostic? +

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

Can I rate-limit run_tracking_diagnostic? +

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

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

run_tracking_diagnostic is provided by the KonQuest Meta Ads MCP server (brandu-mos/konquest-meta-ads-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.