bulk_rename_objects · KonQuest Meta Ads MCP: Risk & Policy

WHAT IT DOES

What bulk_rename_objects does on KonQuest Meta Ads MCP

AI agents use bulk_rename_objects 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 bulk_rename_objects needs a policy

This tool modifies ad campaign objects (renaming) which constitutes a Write operation. The severity is medium because bulk renaming multiple objects could affect campaign organization and reporting, but the operation is reversible—old names could be restored. It is not Destructive (data not deleted), Execute (no arbitrary code/external operations), Financial (no payments), or Read (causes state changes).

From the tool's definition Tool description states 'Rename multiple Meta Ads objects in one call.' Renaming is a reversible modification operation that changes metadata without deleting or destroying data.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bulk_rename_objects Rate-limited

bulk_rename_objects 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": {
    "bulk_rename_objects": {
      "limits": [
        {
          "counter": "bulk_rename_objects_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 bulk_rename_objects

What does the bulk_rename_objects tool do? +

Rename multiple Meta Ads objects in one call. 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 bulk_rename_objects? +

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

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

Can I rate-limit bulk_rename_objects? +

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

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

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