AI agents use create_bidder 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 | Bidder name |
status | string | — | Bidder status |
bid_url | string | — | Bid endpoint URL |
Parameters from the server's own tool schema.
Creating a new bidder modifies the system state by adding a new record, but this is reversible (can be archived or deleted). It does not execute arbitrary code, delete data irreversibly, or move money. The medium severity reflects that misconfigured bidders in an ad system could cause unintended campaign behavior or financial impact, but the tool itself is a straightforward Write operation.
From the tool's definition Tool name 'create_bidder' with description 'Create a new bidder' indicates data creation. Sibling tools include 'archive_*' and 'bulk_upload_*' patterns consistent with a campaign/advertising management system where bidders are reversible entities.
Attacks that exploit this kind of access
Create a new bidder. 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_bidder accepts 3 parameters: name, status, bid_url. 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_bidder: 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_bidder 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_bidder 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_bidder. 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_bidder 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 →