This record as markdown: /tools/adbutler/list-bidders.md
What list_bidders does on AdButler
AI agents call list_bidders to retrieve information from AdButler without modifying anything. It is 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.
Why list_bidders is rated Low
This tool retrieves a list of bidders from the AdButler account. It performs a read-only query operation with no capability to create, modify, delete, or execute external actions. The blast radius of misuse is minimal—an agent could only access bidder information already in the system.
From the tool's definition Tool name 'list_bidders' and description 'List all bidders in your AdButler account' indicate a retrieval operation with the verb 'List', which queries and returns existing data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_bidders 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 list_bidders, this is the rule to start with:
list_bidders is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every list_bidders call is checked against it from then on.
Questions about list_bidders
List all bidders 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_bidders 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_bidders: 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_bidders 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_bidders 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_bidders. 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_bidders 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.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue