get_catalog_zone_tag
Get the ad serving tag for a catalog zone
This record as markdown: /tools/adbutler/get-catalog-zone-tag.md
What get_catalog_zone_tag does on AdButler
AI agents call get_catalog_zone_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 | Catalog zone ID |
Parameters from the server's own tool schema.
Why get_catalog_zone_tag is rated Low
This tool retrieves/queries an existing ad serving tag for a catalog zone. It performs a read-only operation with no side effects, no data modification, no code execution, and no destructive actions. The low severity reflects that exposing tag information has minimal security impact compared to tools that modify campaigns or delete data.
From the tool's definition Tool name 'get_catalog_zone_tag' and description 'Get the ad serving tag for a catalog zone' indicate a retrieval operation with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs get_catalog_zone_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_catalog_zone_tag, this is the rule to start with:
get_catalog_zone_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_catalog_zone_tag call is checked against it from then on.
Questions about get_catalog_zone_tag
Get the ad serving tag for a catalog zone. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
get_catalog_zone_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_catalog_zone_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_catalog_zone_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_catalog_zone_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_catalog_zone_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_catalog_zone_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