AI agents call list_demand_endpoints to retrieve information from AdButler without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max results to return (default 100, max 100) |
offset | number | — | Pagination offset |
Parameters from the server's own tool schema.
The tool retrieves and enumerates existing demand endpoints without creating, modifying, or deleting any data. It is a pure information retrieval function, matching the Read category (search, list, get, fetch). The blast radius of misuse is minimal since listing endpoints poses no risk to system integrity or data.
From the tool's definition Tool name contains 'list' and description states 'List all demand endpoints' — this is a read-only query operation with no side effects.
Attacks that exploit this kind of access
List all demand endpoints in your AdButler account. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
list_demand_endpoints accepts 2 parameters: limit, offset. 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 list_demand_endpoints: 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.
list_demand_endpoints is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_demand_endpoints 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 list_demand_endpoints. 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.
list_demand_endpoints 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 →