delete_config
Delete a config by slug. This is permanent, removes all versions, and breaks anything still pointing at that slug; check list_config_versions first.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/delete-config.md
What delete_config does on Portkey Admin
AI agents call delete_config to permanently remove resources in Portkey Admin, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_config is rated Critical
This tool permanently deletes configuration data and cannot be undone. It removes all historical versions and has cascading effects on systems that depend on the deleted configuration. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone'.
From the tool's definition Description states 'Delete a config by slug. This is permanent, removes all versions, and breaks anything still pointing at that slug'.
Attacks that exploit this kind of access
The rule that runs delete_config 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 delete_config, this is the rule to start with:
delete_config is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Portkey Admin, apply this rule, and every delete_config call is checked against it from then on.
Questions about delete_config
Delete a config by slug. This is permanent, removes all versions, and breaks anything still pointing at that slug; check list_config_versions first. It is categorised as a Destructive tool in the Portkey Admin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for delete_config: 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.
delete_config is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_config 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 delete_config. 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.
delete_config 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.
Across the catalogue