This record as markdown: /tools/adbutler/create-data-key.md
What create_data_key does on AdButler
AI agents use create_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Data key name (max 32 chars, must be unique) |
type | string | Yes | Data key value type |
Parameters from the server's own tool schema.
Why create_data_key is rated Medium
The tool creates (writes) a new targeting data key within the AdButler ad management system. This modifies the system state but is reversible via standard archive/delete operations. It does not execute code, destroy data irreversibly, or involve financial transactions, making Write the appropriate category.
From the tool's definition Tool name 'create_data_key' and description 'Create a new data key for custom targeting' indicate creation of a new resource. The action is reversible (data keys can typically be deleted or archived, as evidenced by sibling tools like 'archive_' operations).
Attacks that exploit this kind of access
The rule that runs create_data_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdButler, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_data_key, this is the rule to start with:
create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every create_data_key call is checked against it from then on.
Questions about create_data_key
Create a new data key for custom targeting. 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.
create_data_key accepts 2 parameters: name, type. Required: name, type. The full parameter table on this page comes from the server's own tool schema.
Register the AdButler MCP server in PolicyLayer and add a rule for create_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.
create_data_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue