list_mcp_integration_workspaces

List which workspaces can access an MCP integration. Returns the global access mode plus per-workspace enablement for audit or permission review; use before update_mcp_integration_workspaces.

SERVERPortkey Admin SOURCEcodeswhat/portkey-admin-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What list_mcp_integration_workspaces does on Portkey Admin

AI agents call list_mcp_integration_workspaces to retrieve information from Portkey Admin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_mcp_integration_workspaces is rated Low

This tool retrieves and reports access control metadata for audit or permission review purposes. It has no side effects, cannot alter system state, and poses minimal risk if queried by an AI agent. The primary concern would be information disclosure of workspace access policies, which is typically low severity in administrative contexts.

From the tool's definition Tool performs a listing/query operation: 'List which workspaces can access an MCP integration. Returns the global access mode plus per-workspace enablement'. No data creation, modification, deletion, or execution of external operations occurs.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_mcp_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 list_mcp_integration_workspaces, this is the rule to start with:

list_mcp_integration_workspaces Allowed

list_mcp_integration_workspaces is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_mcp_integration_workspaces": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about list_mcp_integration_workspaces

What does the list_mcp_integration_workspaces tool do? +

List which workspaces can access an MCP integration. Returns the global access mode plus per-workspace enablement for audit or permission review; use before update_mcp_integration_workspaces. It is categorised as a Read tool in the Portkey Admin MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_mcp_integration_workspaces? +

Register the Portkey Admin MCP server in PolicyLayer and add a rule for list_mcp_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 list_mcp_integration_workspaces? +

list_mcp_integration_workspaces is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_mcp_integration_workspaces? +

Yes. Add a rate_limit block to the list_mcp_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 list_mcp_integration_workspaces completely? +

Set action: deny in the PolicyLayer policy for list_mcp_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 list_mcp_integration_workspaces? +

list_mcp_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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →