Update a config by slug and create a new version. Only provided fields change; name and status are editable, while the slug stays fixed. Use list_config_versions if you need history first.
AI agents use update_config to create or update resources in Portkey Admin — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Portkey Admin environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | New name for the configuration |
slug | string | Yes | Configuration slug to update |
status | string | — | Configuration status |
targets | array | — | Array of target providers |
cache_mode | string | — | Cache mode: 'simple' or 'semantic' |
cache_max_age | number | — | Cache max age in seconds |
strategy_mode | string | — | Routing strategy |
retry_attempts | number | — | Number of retry attempts (1-5) |
retry_on_status_codes | array | — | HTTP status codes to retry on |
Parameters from the server's own tool schema.
An AI agent can call update_config faster than any human can review — one bad instruction and it creates or modifies resources in Portkey Admin by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
Update a config by slug and create a new version. Only provided fields change; name and status are editable, while the slug stays fixed. Use list_config_versions if you need history first. It is categorised as a Write tool in the Portkey Admin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_config accepts 9 parameters: name, slug, status, targets, cache_mode, cache_max_age, strategy_mode, retry_attempts, retry_on_status_codes. Required: slug. The full parameter table on this page comes from the server's own tool schema.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for update_config: 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 Portkey Admin. Nothing to install.
update_config 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_config 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_config. 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_config is provided by the Portkey Admin MCP server (CodesWhat/portkey-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.