list_providers

List workspace-scoped provider instances and their limits or status. Use this to find provider slugs for workspace-level updates; use list_integrations for the org-level source connection. Returns total plus provider name, slug, integration, status, limits, expiration, and reset flags.

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-providers.md

WHAT IT DOES

What list_providers does on Portkey Admin

AI agents call list_providers 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_providers is rated Low

This tool queries and retrieves information about provider instances within a workspace. It performs no write operations, does not execute code, and does not delete or move data. The act of listing or reading existing configuration data is a Read category operation with low severity, as unauthorized access to provider metadata poses limited immediate risk compared to tools that modify or delete data.

From the tool's definition Tool description states it 'List[s]' workspace-scoped provider instances and returns metadata (name, slug, integration, status, limits, expiration, reset flags).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_providers Allowed

list_providers 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_providers": {}
  }
}

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_providers call is checked against it from then on.

FAQ

Questions about list_providers

What does the list_providers tool do? +

How do I enforce a policy on list_providers? +

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

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

Can I rate-limit list_providers? +

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

Set action: deny in the PolicyLayer policy for list_providers. 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_providers? +

list_providers 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 →