generate_names · KonQuest Meta Ads MCP: Risk & Policy

WHAT IT DOES

What generate_names does on KonQuest Meta Ads MCP

AI agents use generate_names to create or update resources in KonQuest Meta Ads MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your KonQuest Meta Ads MCP environment.

WHY IT NEEDS A POLICY

Why generate_names needs a policy

The tool likely creates or generates ad names/copy for campaigns (Write category). Without seeing actual functionality, confidence is moderate. In the context of ad management, generated names typically become persistent campaign assets that require approval/cleanup if unwanted, making it Write rather than Read.

From the tool's definition Tool name 'generate_names' suggests content generation/creation; context of Meta Ads MCP with sibling tools like 'create_ad_creative' and 'create_campaign' indicates this generates naming assets for ad campaigns. Description is empty, limiting certainty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_names Rate-limited

generate_names stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_names": {
      "limits": [
        {
          "counter": "generate_names_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 generate_names

What does the generate_names tool do? +

generate_names. It is categorised as a Write tool in the KonQuest Meta Ads MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_names? +

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

generate_names is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit generate_names? +

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

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

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