list_data_key_targets
List all data key targets (targeting rules using data key values)
This record as markdown: /tools/adbutler/list-data-key-targets.md
What list_data_key_targets does on AdButler
AI agents call list_data_key_targets to retrieve information from AdButler without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max results to return (default 100, max 100) |
offset | number | — | Pagination offset |
Parameters from the server's own tool schema.
Why list_data_key_targets is rated Low
This is a read-only query operation that retrieves existing targeting rule configurations. It has no side effects and poses minimal risk; an AI agent misusing it would only see targeting metadata, not cause harm to campaigns, finances, or data integrity.
From the tool's definition Tool name contains 'list' and description states 'List all data key targets' — retrieves targeting rules without modifying, creating, or deleting data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs list_data_key_targets 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 list_data_key_targets, this is the rule to start with:
list_data_key_targets is read-only, so it stays allowed. 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 list_data_key_targets call is checked against it from then on.
Questions about list_data_key_targets
List all data key targets (targeting rules using data key values). It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
list_data_key_targets accepts 2 parameters: limit, offset. 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 list_data_key_targets: 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.
list_data_key_targets is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_data_key_targets 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 list_data_key_targets. 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.
list_data_key_targets 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