get_product_source_target
Get details of a specific product source target
This record as markdown: /tools/adbutler/get-product-source-target.md
What get_product_source_target does on AdButler
AI agents call get_product_source_target 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 |
|---|---|---|---|
publisher_id | number | Yes | Publisher ID |
source_target_id | number | Yes | Source target ID |
Parameters from the server's own tool schema.
Why get_product_source_target is rated Low
This tool retrieves or queries existing product source target details without creating, modifying, deleting, or executing operations. It is a straightforward data retrieval function, placing it in the Read category with low severity since unauthorized access to advertising configuration details poses minimal immediate risk compared to write or destructive operations.
From the tool's definition Tool name 'get_product_source_target' and description 'Get details of a specific product source target' indicate a retrieval operation with no modification of data.
Attacks that exploit this kind of access
The rule that runs get_product_source_target 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 get_product_source_target, this is the rule to start with:
get_product_source_target 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 get_product_source_target call is checked against it from then on.
Questions about get_product_source_target
Get details of a specific product source target. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
get_product_source_target accepts 2 parameters: publisher_id, source_target_id. Required: publisher_id, source_target_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_product_source_target: 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_product_source_target 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_product_source_target 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_product_source_target. 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_product_source_target 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