create_zobject
Create a new zobject (custom metadata instance). Must specify which zobject_type it belongs to.
This record as markdown: /tools/com-zype-mcp-server/create-zobject.md
What create_zobject does on Zype Com
AI agents use create_zobject 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 |
|---|---|---|---|
title | string | Yes | Title of the zobject (required) |
active | boolean | — | Whether the zobject is active (default: true) |
custom | object | — | Custom attributes as key-value pairs |
video_ids | array | — | Array of video IDs to associate |
description | string | — | Description |
playlist_ids | array | — | Array of playlist IDs to associate |
friendly_title | string | — | URL-friendly title (slug) |
zobject_type_id | string | Yes | ID of the zobject type this zobject belongs to (required) |
Parameters from the server's own tool schema.
Why create_zobject is rated Medium
An AI agent can call create_zobject 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 create_zobject 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 create_zobject, this is the rule to start with:
create_zobject 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 create_zobject call is checked against it from then on.
Questions about create_zobject
Create a new zobject (custom metadata instance). Must specify which zobject_type it belongs to. 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.
create_zobject accepts 8 parameters: title, active, custom, video_ids, description, playlist_ids, friendly_title, zobject_type_id. Required: title, zobject_type_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 create_zobject: 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.
create_zobject 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 create_zobject 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 create_zobject. 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.
create_zobject 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