list_integration_workspaces
List workspaces that can use an integration, with their limits. Use this to audit access or confirm per-workspace cost and rate settings. Returns total plus workspace ids, names, enabled state, usage limits, and rate limits.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/list-integration-workspaces.md
What list_integration_workspaces does on Portkey Admin
AI agents call list_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.
Why list_integration_workspaces is rated Low
This tool retrieves and queries data about workspace integrations and their limits for audit purposes. It has no side effects, does not modify or delete data, does not execute code, and does not involve financial transactions. It is a straightforward Read operation that enables visibility into existing system configuration.
From the tool's definition Tool name 'list_integration_workspaces' and description explicitly states 'List workspaces' and 'Returns total plus workspace ids, names, enabled state, usage limits, and rate limits' — purely retrieval of configuration and audit data with no modification,…
Attacks that exploit this kind of access
The rule that runs list_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_integration_workspaces, this is the rule to start with:
list_integration_workspaces is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Portkey Admin, apply this rule, and every list_integration_workspaces call is checked against it from then on.
Questions about list_integration_workspaces
List workspaces that can use an integration, with their limits. Use this to audit access or confirm per-workspace cost and rate settings. Returns total plus workspace ids, names, enabled state, usage limits, and rate limits. It is categorised as a Read tool in the Portkey Admin MCP Server, which means it retrieves data without modifying state.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for list_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.
list_integration_workspaces is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_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.
Set action: deny in the PolicyLayer policy for list_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.
list_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.
More on Portkey Admin, and thousands of servers like it.
This server
Across the catalogue