create_platform_target
Create a new platform target for device/OS/browser targeting
This record as markdown: /tools/adbutler/create-platform-target.md
What create_platform_target does on AdButler
AI agents use create_platform_target 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 | Platform target name |
platform | string | — | Preset platform target (default: any) |
device_targets | array | — | List of device patterns to target (e.g. "Apple*", "Samsung Galaxy S5") |
Parameters from the server's own tool schema.
Why create_platform_target is rated Medium
The tool creates a new targeting configuration within AdButler's campaign management system. This is a reversible write operation that modifies campaign data but does not delete, execute arbitrary code, or move money.
From the tool's definition Tool name 'create_platform_target' with description 'Create a new platform target' indicates data creation. The sibling tools include 'archive_*' (destructive) and 'bulk_create_*' operations, confirming this server handles campaign management modifications.
Attacks that exploit this kind of access
The rule that runs create_platform_target 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_platform_target, this is the rule to start with:
create_platform_target 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_platform_target call is checked against it from then on.
Questions about create_platform_target
Create a new platform target for device/OS/browser 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_platform_target accepts 3 parameters: name, platform, device_targets. Required: name. 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_platform_target: 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_platform_target 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_platform_target 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_platform_target. 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_platform_target 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