AI agents use create_geo_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 | Geo target name |
unit | string | — | Distance unit for range |
areas | array | Yes | Array of geographic areas to target |
range | number | — | Radius range for geo-fencing (only applies when targeting a city) |
inclusive | boolean | — | If true, target users IN these areas; if false, EXCLUDE these areas |
Parameters from the server's own tool schema.
This tool creates new geo targeting configuration that modifies campaign behavior and targeting settings. It is reversible (can be archived or deleted based on sibling tools like 'archive_zone'), making it a Write operation rather than Destructive.
From the tool's definition Tool name 'create_geo_target' and description 'Create a new geo target' indicate data creation. The tool takes configuration input (continent, country, region, city fields) and persists a new targeting entity.
Attacks that exploit this kind of access
Create a new geo target for geographic targeting. Areas is an array of objects with continent, country (2-letter code), region, city fields. 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_geo_target accepts 5 parameters: name, unit, areas, range, inclusive. Required: name, areas. 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_geo_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_geo_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_geo_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_geo_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_geo_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 →