run_setup_check · KonQuest Meta Ads MCP: Risk & Policy

WHAT IT DOES

What run_setup_check does on KonQuest Meta Ads MCP

AI agents invoke run_setup_check 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_setup_check needs a policy

The 'run_' prefix combined with 'setup_check' suggests automated execution of diagnostic/setup routines rather than simple data retrieval. Given the sibling tools involve financial operations (ad campaigns, creative assets), this setup check likely performs initialization, validation, or configuration operations that could affect campaign state or financial systems.

From the tool's definition Tool name 'run_setup_check' uses the verb 'run', which indicates execution of diagnostic or setup operations. The server context involves Meta Ads campaign management with financial implications. Description is empty, limiting direct confirmation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_setup_check Rate-limited

run_setup_check 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_setup_check": {
      "limits": [
        {
          "counter": "run_setup_check_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_setup_check

What does the run_setup_check tool do? +

run_setup_check. 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_setup_check? +

Register the KonQuest Meta Ads MCP server in PolicyLayer and add a rule for run_setup_check: 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_setup_check? +

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

Can I rate-limit run_setup_check? +

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

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

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