update_integration_workspaces · Portkey Admin MCP

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.

PARAMETERS

Parameter	Type	Required	Description
`slug`	string	Yes	The slug of the integration
`workspaces`	array	Yes	Array of workspace configurations to update

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why update_integration_workspaces needs a policy

An AI agent can call update_integration_workspaces 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.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Portkey Admin, so you can run agents against it safely.

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.

What parameters does update_integration_workspaces accept? +

update_integration_workspaces accepts 2 parameters: slug, workspaces. Required: slug, workspaces. The full parameter table on this page comes from the server's own tool schema.

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.