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.
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
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →