delete_integration_model
Delete a custom model from an integration. Built-in models should be disabled instead, because deletion only applies to custom entries. Returns success after the custom model is removed.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/delete-integration-model.md
What delete_integration_model does on Portkey Admin
AI agents call delete_integration_model 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_integration_model is rated Critical
Deletion of data without reversibility is the defining characteristic of the Destructive category. While the blast radius is scoped to a single custom model entry (mitigating against 'critical'), the irreversible removal of configuration data warrants 'high' severity. An AI agent with access to this tool could permanently destroy custom model integrations without recovery options.
From the tool's definition Tool name contains 'delete' and description states 'after the custom model is removed' — this is an irreversible deletion operation. The tool removes custom model entries from an integration permanently.
Attacks that exploit this kind of access
The rule that runs delete_integration_model 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_integration_model, this is the rule to start with:
delete_integration_model 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_integration_model call is checked against it from then on.
Questions about delete_integration_model
Delete a custom model from an integration. Built-in models should be disabled instead, because deletion only applies to custom entries. Returns success after the custom model is removed. 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_integration_model: 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_integration_model 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_integration_model 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_integration_model. 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_integration_model 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