update_integration_workspaces

SERVERPortkey Admin SOURCEcodeswhat/portkey-admin-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/codeswhat-portkey-admin-mcp/update-integration-workspaces.md

WHAT IT DOES

What update_integration_workspaces does on Portkey Admin

AI agents use update_integration_workspaces 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.

RISK

Why update_integration_workspaces is rated Medium

This tool modifies access control lists and workspace-level configuration for integrations. While reversible (access can be re-granted, limits can be adjusted), it directly impacts which users/workspaces can access integrations and enforces usage limits. Changes 'apply to downstream usage immediately,' suggesting active enforcement.

From the tool's definition Tool description states it controls 'which workspaces can use an integration and set per-workspace limits' and 'access changes and new limits apply to downstream usage immediately.' The verb 'Control' and explicit mention of setting limits and access changes…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_integration_workspaces safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Portkey Admin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_integration_workspaces, this is the rule to start with:

update_integration_workspaces Rate-limited

update_integration_workspaces 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_integration_workspaces": {
      "limits": [
        {
          "counter": "update_integration_workspaces_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Portkey Admin, apply this rule, and every update_integration_workspaces call is checked against it from then on.

FAQ

Questions about update_integration_workspaces

What does the update_integration_workspaces tool do? +

Control which workspaces can use an integration and set per-workspace limits, unlike update_integration which edits the org-level connection. Call list_integration_workspaces first to review current state; access changes and new limits apply to downstream usage immediately, and the call returns success plus the number of workspaces updated. 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.

How do I enforce a policy on update_integration_workspaces? +

Register the Portkey Admin MCP server in PolicyLayer and add a rule for update_integration_workspaces: 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.

What risk level is update_integration_workspaces? +

update_integration_workspaces is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_integration_workspaces? +

Yes. Add a rate_limit block to the update_integration_workspaces 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.

How do I block update_integration_workspaces completely? +

Set action: deny in the PolicyLayer policy for update_integration_workspaces. 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.

What MCP server provides update_integration_workspaces? +

update_integration_workspaces 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.

KEEP EXPLORING

More on Portkey Admin, and thousands of servers like it.

This server

All 156 Portkey Admin tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →