update_data_key · AdButler MCP: Risk & Policy

WHAT IT DOES

What update_data_key does on AdButler

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

PARAMETERS

Parameter	Type	Required	Description
`id`	number	Yes	Data key ID
`name`	string	—	Data key name
`type`	string	—	Data key value type

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why update_data_key needs a policy

This tool modifies data reversibly (updates rather than deletes), placing it in the Write category. Severity is medium because unintended updates to data keys could corrupt advertising configuration or targeting data, affecting campaigns and reporting, but the change is not irreversible (can be updated again) and does not involve deletion, financial transactions, or arbitrary code execution.

From the tool's definition Tool name 'update_data_key' with description 'Update an existing data key' indicates modification of existing data in the AdButler advertising management system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_data_key Rate-limited

update_data_key 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": {
    "update_data_key": {
      "limits": [
        {
          "counter": "update_data_key_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 AdButler, so you can run agents against it safely.

FAQ

Questions about update_data_key

What does the update_data_key tool do? +

Update an existing data key. It is categorised as a Write tool in the AdButler MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_data_key accept? +

update_data_key accepts 3 parameters: id, name, type. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_data_key? +

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

What risk level is update_data_key? +

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

Can I rate-limit update_data_key? +

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

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

update_data_key is provided by the AdButler MCP server (adbutler/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.