create_demand_endpoint

Create a new demand endpoint

SERVERAdButler SOURCEadbutler/mcp-server

Medium RISK CLASS

Category Write

Parameters 123 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adbutler/create-demand-endpoint.md

WHAT IT DOES

What create_demand_endpoint does on AdButler

AI agents use create_demand_endpoint 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	Demand endpoint name
`status`	string	—	Whether to send bid requests (default: active)
`priority`	string	—	Serving priority
`bid_floor`	number	—	Default CPM bid floor
`geo_target`	number	—	Geo target ID for geographic targeting
`filter_type`	string	—	Zone filtering type
`allowed_sizes`	array	—	Allowed zone sizes (e.g. ["300x250", "728x90"])
`demand_source`	number	Yes	Demand Source ID this endpoint belongs to
`revenue_share`	number	—	Revenue share percentage paid to publisher
`filtered_zones`	array	—	Zone IDs for the filter list
`markup_percent`	number	—	Markup percent applied to zone bid floor
`supported_formats`	array	Yes	Supported ad formats: "display", "native", "video"

Parameters from the server's own tool schema.

RISK

Why create_demand_endpoint is rated Medium

This tool creates a new demand endpoint, which is a reversible write operation that modifies system configuration by adding a new entity. It does not delete data (not Destructive), does not execute arbitrary code (not Execute), does not handle financial transactions directly (not Financial), and retrieves no data (not Read).

From the tool's definition Tool name 'create_demand_endpoint' and description 'Create a new demand endpoint' indicate creation of a new configuration object within AdButler's advertising management system.

Risk signalsHigh parameter count (15 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_demand_endpoint 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_demand_endpoint, this is the rule to start with:

create_demand_endpoint Rate-limited

create_demand_endpoint 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_demand_endpoint": {
      "limits": [
        {
          "counter": "create_demand_endpoint_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every create_demand_endpoint call is checked against it from then on.

FAQ

Questions about create_demand_endpoint

What does the create_demand_endpoint tool do? +

Create a new demand endpoint. 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.

What parameters does create_demand_endpoint accept? +

create_demand_endpoint accepts 12 parameters: name, status, priority, bid_floor, geo_target, filter_type, allowed_sizes, demand_source, revenue_share, filtered_zones, markup_percent, supported_formats. Required: name, demand_source, supported_formats. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_demand_endpoint? +

Register the AdButler MCP server in PolicyLayer and add a rule for create_demand_endpoint: 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.

What risk level is create_demand_endpoint? +

create_demand_endpoint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_demand_endpoint? +

Yes. Add a rate_limit block to the create_demand_endpoint 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.

How do I block create_demand_endpoint completely? +

Set action: deny in the PolicyLayer policy for create_demand_endpoint. 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.

What MCP server provides create_demand_endpoint? +

create_demand_endpoint 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.

KEEP EXPLORING

More on AdButler, and thousands of servers like it.

This server

All 622 AdButler tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →