portkey-admin-mcp

update_integration_workspaces

DestructiveIdempotent

Update per-workspace and global access to an integration by setting cost/rate limits, resetting usage, and creating default providers; review current workspace settings first to prevent unintended access changes.

Instructions

Control per-workspace and global access to an integration, including cost/rate limits, usage resets, and automatic default-provider creation. global_workspace_access_enabled affects current and future workspaces; override_existing_workspace_access determines whether it replaces explicit workspace settings. Per-workspace default-provider fields override top-level values. Review list_integration_workspaces first because access and limits change downstream usage immediately.

Input Schema

Name	Required	Description
`slug`	Yes	The slug of the integration
`workspaces`	Yes	Array of workspace configurations to update
`global_credit_limit`	No	Global cost credit limit applied with global workspace access
`default_provider_slug`	No	Default slug for providers auto-created in workspaces
`global_rate_limit_rpm`	No	Global requests-per-minute limit for workspace access
`global_alert_threshold`	No	Global cost alert threshold applied to workspace access
`create_default_provider`	No	Auto-create providers when granting workspace access
`global_workspace_access_enabled`	No	Enable or disable access for all current and future workspaces
`override_existing_workspace_access`	No	Apply global settings over existing per-workspace access

Output Schema

Name	Required	Description
`ok`	Yes	Whether the tool call succeeded and returned structured data
`data`	No	Structured success payload when ok is true
`error`	No	Structured error payload when ok is false

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.9Oct 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed10 schema fields changedAug 9, 2026

addedInput schema / properties / create_default_provider

Added value: +{
+  "description": "Auto-create providers when granting workspace access",
+  "type": "boolean"
+}

addedInput schema / properties / default_provider_slug

Added value: +{
+  "description": "Default slug for providers auto-created in workspaces",
+  "type": "string"
+}

addedInput schema / properties / global_alert_threshold

Added value: +{
+  "description": "Global cost alert threshold applied to workspace access",
+  "maximum": 100,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / global_credit_limit

Added value: +{
+  "description": "Global cost credit limit applied with global workspace access",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}

addedInput schema / properties / global_rate_limit_rpm

Added value: +{
+  "description": "Global requests-per-minute limit for workspace access",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}

addedInput schema / properties / global_workspace_access_enabled

Added value: +{
+  "description": "Enable or disable access for all current and future workspaces",
+  "type": "boolean"
+}

addedInput schema / properties / override_existing_workspace_access

Added value: +{
+  "description": "Apply global settings over existing per-workspace access",
+  "type": "boolean"
+}

addedInput schema / properties / workspaces / items / properties / create_default_provider

Added value: +{
+  "description": "Override whether a provider is auto-created for this workspace",
+  "type": "boolean"
+}

addedInput schema / properties / workspaces / items / properties / default_provider_slug

Added value: +{
+  "description": "Override the auto-created provider slug for this workspace",
+  "type": "string"
+}

addedInput schema / properties / workspaces / items / properties / reset_usage

Added value: +{
+  "description": "Reset exhausted usage status to active",
+  "type": "boolean"
+}

Addedv1.0.1May 7, 2026
RemovedMay 1, 2026
First observedJan 1, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description explains that global_workspace_access_enabled affects current and future workspaces, override_existing_workspace_access replaces explicit workspace settings, and per-workspace defaults override top-level values. It also warns that access and limits change downstream usage immediately, which meaningfully clarifies the destructive and broad effects of the operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four tight sentences, front-loaded with the tool's scope and then the key precedence rules and prerequisite. Every sentence adds operational meaning without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex, destructive mutation tool with rich annotations and an output schema, the description covers scope, key flag interactions, precedence, immediate downstream impact, and a prerequisite read. Return values need not be described because an output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is already 100%, so the baseline is 3. The description adds value by explaining precedence interactions: global_workspace_access_enabled affects current and future workspaces, override_existing_workspace_access determines replacement of explicit settings, and per-workspace default-provider fields override top-level values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and action: controlling per-workspace and global access to an integration, including cost/rate limits, resets, and default-provider creation. It also distinguishes this from the sibling list_integration_workspaces by recommending that tool as a prerequisite read.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context and a prerequisite: review list_integration_workspaces first because access and limits change downstream usage immediately. It does not explicitly state when not to use this tool or name a specific alternative for non-workspace integration updates, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server