AI agents call get_demand_source 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 |
|---|---|---|---|
id | number | Yes | Demand source ID |
Parameters from the server's own tool schema.
The tool retrieves information about a demand source without creating, modifying, deleting, or executing external operations. This is a standard read-only query operation with minimal risk if misused by an AI agent, as it only exposes existing data.
From the tool's definition Tool name 'get_demand_source' and description 'Get details of a specific demand source by ID' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get details of a specific demand source by ID. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
get_demand_source accepts 1 parameter: id. Required: id. 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 get_demand_source: 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.
get_demand_source 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 get_demand_source 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 get_demand_source. 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.
get_demand_source 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 →