list_config_versions

List every version of a config with version_id, structured config payload, updater, and timestamp. Use this to audit history or compare revisions before update_config or delete_config.

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-config-versions.md

WHAT IT DOES

What list_config_versions does on Portkey Admin

AI agents call list_config_versions 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_config_versions is rated Low

Tool retrieves configuration version history with no side effects or modifications.

From the tool's definition List every version of a config with version_id, structured config payload, updater, and timestamp.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_config_versions Allowed

list_config_versions 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_config_versions": {}
  }
}

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

FAQ

Questions about list_config_versions

What does the list_config_versions tool do? +

List every version of a config with version_id, structured config payload, updater, and timestamp. Use this to audit history or compare revisions before update_config or delete_config. 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_config_versions? +

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

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

Can I rate-limit list_config_versions? +

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

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

list_config_versions 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 170 Portkey Admin tools →

Across the catalogue

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

Guides

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