get_native_ad_item_conversion_tag
Get conversion tracking tag for a native ad item
This record as markdown: /tools/adbutler/get-native-ad-item-conversion-tag.md
What get_native_ad_item_conversion_tag does on AdButler
AI agents call get_native_ad_item_conversion_tag 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 |
|---|---|---|---|
id | number | Yes | Ad item ID |
Parameters from the server's own tool schema.
Why get_native_ad_item_conversion_tag is rated Low
This tool retrieves a conversion tracking tag for an existing native ad item. It performs a query/fetch operation without any side effects—no data is created, modified, deleted, or executed. It falls squarely into the Read category. Severity is low because exposure of a conversion tag itself poses minimal risk (tags are typically non-sensitive identifiers used for tracking purposes).
From the tool's definition Tool name 'get_native_ad_item_conversion_tag' uses 'get' prefix; description states 'Get conversion tracking tag', indicating a retrieval operation with no modification.
Attacks that exploit this kind of access
The rule that runs get_native_ad_item_conversion_tag 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_native_ad_item_conversion_tag, this is the rule to start with:
get_native_ad_item_conversion_tag 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_native_ad_item_conversion_tag call is checked against it from then on.
Questions about get_native_ad_item_conversion_tag
Get conversion tracking tag for a native ad item. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
get_native_ad_item_conversion_tag 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_native_ad_item_conversion_tag: 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_native_ad_item_conversion_tag 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_native_ad_item_conversion_tag 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_native_ad_item_conversion_tag. 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_native_ad_item_conversion_tag 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