list_configs
List configs in the org with id, slug, name, status, workspace, and timestamps. Use this summary view to find a slug; use get_config for the full routing, cache, retry, and target settings before updating or deleting.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/list-configs.md
What list_configs does on Portkey Admin
AI agents call list_configs 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_configs is rated Low
This tool retrieves and queries configuration data from the Portkey Admin API without modifying, deleting, or executing any operations. It is explicitly a 'summary view' for listing existing configs. No side effects or state changes occur; it is a pure read operation that returns metadata about configurations.
From the tool's definition List configs in the org with id, slug, name, status, workspace, and timestamps. Use this summary view to find a slug...
Attacks that exploit this kind of access
The rule that runs list_configs 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_configs, this is the rule to start with:
list_configs 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_configs call is checked against it from then on.
Questions about list_configs
List configs in the org with id, slug, name, status, workspace, and timestamps. Use this summary view to find a slug; use get_config for the full routing, cache, retry, and target settings before updating or deleting. 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_configs: 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_configs 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_configs 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_configs. 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_configs 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