update_firewall_rule
Полностью обновляет правило firewall. Передаются direction, protocol (обязательно) и опциональные port, cidr, description — эти поля перезаписывают текущие значения правила.
This record as markdown: /tools/timeweb-mcp/update-firewall-rule.md
What update_firewall_rule does on Timeweb
AI agents use update_firewall_rule to create or update resources in Timeweb, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Timeweb environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
cidr | string | — | Сетевой адрес или подсеть (IPv4/IPv6, CIDR) |
port | string | — | Порт или диапазон портов (только для tcp/udp) |
rule_id | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID правила |
group_id | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID группы правил firewall |
protocol | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - протокол: tcp, udp или icmp |
direction | string | Yes | ОБЯЗАТЕЛЬНОЕ ПОЛЕ - направление трафика: ingress или egress |
description | string | — | Описание правила (опц.) |
Parameters from the server's own tool schema.
Why update_firewall_rule is rated Medium
An AI agent can call update_firewall_rule faster than any human can review: one bad instruction and it creates or modifies resources in Timeweb by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs update_firewall_rule safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Timeweb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_firewall_rule, this is the rule to start with:
update_firewall_rule 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 Timeweb, apply this rule, and every update_firewall_rule call is checked against it from then on.
Questions about update_firewall_rule
Полностью обновляет правило firewall. Передаются direction, protocol (обязательно) и опциональные port, cidr, description — эти поля перезаписывают текущие значения правила. It is categorised as a Write tool in the Timeweb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_firewall_rule accepts 7 parameters: cidr, port, rule_id, group_id, protocol, direction, description. Required: rule_id, group_id, protocol, direction. The full parameter table on this page comes from the server's own tool schema.
Register the Timeweb MCP server in PolicyLayer and add a rule for update_firewall_rule: 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 Timeweb. Nothing to install.
update_firewall_rule 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_firewall_rule 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_firewall_rule. 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_firewall_rule is provided by the Timeweb MCP server (timeweb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Timeweb, and thousands of servers like it.
This server
Across the catalogue