update_content_rule_group
Update an existing content rule group. Only the fields you provide are changed.
This record as markdown: /tools/com-zype-mcp-server/update-content-rule-group.md
What update_content_rule_group does on Zype Com
AI agents use update_content_rule_group 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 |
|---|---|---|---|
name | string | — | New name |
cities | array | — | City names; required for city groups |
states | array | — | US state codes (uppercase); required for state groups |
countries | array | — | ISO 3166-1 alpha-2 country codes (uppercase); required for country groups |
dma_codes | array | — | DMA codes; required for dma_code groups |
ip_ranges | array | — | Start/end IP address pairs |
zip_codes | array | — | ZIP/postal codes; required for zip_code groups |
group_type | string | — | Rule matching type (default: country) |
ip_addresses | array | — | Single hosts or CIDR blocks |
content_rule_group_id | string | Yes | The unique ID of the content rule group to update (required) |
Parameters from the server's own tool schema.
Why update_content_rule_group is rated Medium
An AI agent can call update_content_rule_group 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 signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs update_content_rule_group 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_content_rule_group, this is the rule to start with:
update_content_rule_group 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_content_rule_group call is checked against it from then on.
Questions about update_content_rule_group
Update an existing content rule group. 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_content_rule_group accepts 10 parameters: name, cities, states, countries, dma_codes, ip_ranges, zip_codes, group_type, ip_addresses, content_rule_group_id. Required: content_rule_group_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_content_rule_group: 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_content_rule_group 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_content_rule_group 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_content_rule_group. 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_content_rule_group 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