This record as markdown: /tools/com-zype-mcp-server/update-category.md
What update_category does on Zype Com
AI agents use update_category 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 | — | New title |
values | array | — | New array of possible values |
category_id | string | Yes | The unique ID of the category to update (required) |
friendly_title | string | — | New URL-friendly title |
Parameters from the server's own tool schema.
Why update_category is rated Medium
This tool creates or modifies data reversibly through an update operation on a category. It does not delete data (Destructive), move money (Financial), execute arbitrary code (Execute), or merely read data (Read).
From the tool's definition Tool description explicitly states 'Update an existing category' which modifies existing data in the Thinkific site structure.
Attacks that exploit this kind of access
The rule that runs update_category 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_category, this is the rule to start with:
update_category 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_category call is checked against it from then on.
Questions about update_category
Update an existing category. 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_category accepts 4 parameters: title, values, category_id, friendly_title. Required: category_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_category: 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_category 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_category 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_category. 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_category 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