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

playout_get_published

View Channel's Published. Playout Scheduler (Published Versions).

SERVERZype Com SOURCEzype/zype-mcp
Low RISK CLASS
Category Read
Parameters 21 required
Recommended Allowedsee the rule below
Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/com-zype-mcp-server/playout-get-published.md

What playout_get_published does on Zype Com

AI agents call playout_get_published to retrieve information from Zype Com without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
id string Yes id (required)
starts_at string — startsAt

Parameters from the server's own tool schema.

Why playout_get_published is rated Low

Even though playout_get_published only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about playout_get_published

What does the playout_get_published tool do? +

View Channel's Published. Playout Scheduler (Published Versions). It is categorised as a Read tool in the Zype Com MCP Server, which means it retrieves data without modifying state.

What parameters does playout_get_published accept? +

playout_get_published accepts 2 parameters: id, starts_at. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on playout_get_published? +

Register the Zype Com MCP server in PolicyLayer and add a rule for playout_get_published: 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 playout_get_published? +

playout_get_published is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit playout_get_published? +

Yes. Add a rate_limit block to the playout_get_published 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 playout_get_published completely? +

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

playout_get_published 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.