add_playlists_to_plan
Add playlists to a tiered subscription plan.
This record as markdown: /tools/com-zype-mcp-server/add-playlists-to-plan.md
What add_playlists_to_plan does on Zype Com
AI agents use add_playlists_to_plan 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
plan_id | string | Yes | The plan ID (required) |
playlist_ids | array | Yes | Playlist IDs to add (required) |
Parameters from the server's own tool schema.
Why add_playlists_to_plan is rated Medium
An AI agent can call add_playlists_to_plan 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.
Attacks that exploit this kind of access
The rule that runs add_playlists_to_plan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zype Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_playlists_to_plan, this is the rule to start with:
add_playlists_to_plan stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Zype Com, apply this rule, and every add_playlists_to_plan call is checked against it from then on.
Questions about add_playlists_to_plan
Add playlists to a tiered subscription plan. 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.
add_playlists_to_plan accepts 2 parameters: plan_id, playlist_ids. Required: plan_id, playlist_ids. The full parameter table on this page comes from the server's own tool schema.
Register the Zype Com MCP server in PolicyLayer and add a rule for add_playlists_to_plan: 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.
add_playlists_to_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_playlists_to_plan 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 add_playlists_to_plan. 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.
add_playlists_to_plan 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.
This server
Across the catalogue