New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

create_ad_tag

Create a new VAST/VMAP ad tag.

SERVERZype Com SOURCEzype/zype-mcp
Medium RISK CLASS
Category Write
Parameters 52 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/com-zype-mcp-server/create-ad-tag.md

What create_ad_tag does on Zype Com

AI agents use create_ad_tag to create or update resources in Zype Com, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zype Com environment.

ParameterTypeRequiredDescription
tag string Yes The VAST/VMAP ad tag URL
name string Yes Ad tag name
vmap boolean — Whether this is a VMAP tag
scope string — Ad tag scope
active boolean — Whether the ad tag is active (default: true)

Parameters from the server's own tool schema.

Why create_ad_tag is rated Medium

An AI agent can call create_ad_tag faster than any human can review: one bad instruction and it creates or modifies resources in Zype Com by the hundred, each call as confident as the last.

Questions about create_ad_tag

What does the create_ad_tag tool do? +

Create a new VAST/VMAP ad tag. It is categorised as a Write tool in the Zype Com MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does create_ad_tag accept? +

create_ad_tag accepts 5 parameters: tag, name, vmap, scope, active. Required: tag, name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_ad_tag? +

Register the Zype Com MCP server in PolicyLayer and add a rule for create_ad_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 Zype Com. Nothing to install.

What risk level is create_ad_tag? +

create_ad_tag is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_ad_tag? +

Yes. Add a rate_limit block to the create_ad_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.

How do I block create_ad_tag completely? +

Set action: deny in the PolicyLayer policy for create_ad_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.

What MCP server provides create_ad_tag? +

create_ad_tag is provided by the Zype Com MCP server (zype/zype-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Zype Com, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Zype Com's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.