update_program_guide
Update an existing program guide. Only the fields you provide are changed.
This record as markdown: /tools/com-zype-mcp-server/update-program-guide.md
What update_program_guide does on Zype Com
AI agents use update_program_guide 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 |
|---|---|---|---|
url | string | — | New source URL |
name | string | — | New name |
language | object | — | Language code(s), e.g. 'en' or ['en', 'fr'] |
time_zone | string | — | New time zone |
video_ids | array | — | New set of associated video IDs |
program_guide_id | string | Yes | The unique ID of the program guide to update (required) |
Parameters from the server's own tool schema.
Why update_program_guide is rated Medium
An AI agent can call update_program_guide 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.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs update_program_guide 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 update_program_guide, this is the rule to start with:
update_program_guide 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 update_program_guide call is checked against it from then on.
Questions about update_program_guide
Update an existing program guide. Only the fields you provide are changed. 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.
update_program_guide accepts 6 parameters: url, name, language, time_zone, video_ids, program_guide_id. Required: program_guide_id. 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 update_program_guide: 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.
update_program_guide 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 update_program_guide 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 update_program_guide. 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.
update_program_guide 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