Create a workspace provider backed by an org integration. The provider inherits the integration key, but its limits and expiration are enforced independently for that workspace. Returns the new provider id and slug.
AI agents use create_provider to create or update resources in Portkey Admin — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Portkey Admin environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Display name for the provider |
note | string | — | Optional note or description for the provider |
slug | string | — | Custom slug for the provider. Auto-generated with random suffix if omitted |
expires_at | string | — | Expiration date in ISO 8601 format |
credit_limit | number | — | Credit limit for usage |
workspace_id | string | — | Workspace ID - required when using organization admin API keys |
integration_id | string | Yes | Integration slug for the provider (e.g., 'openai', 'anthropic', 'azure-openai') |
periodic_reset | string | — | Period for resetting usage limits: 'monthly' or 'weekly'. Defaults to 'monthly'. |
alert_threshold | number | — | Alert threshold percentage (0-100) |
rate_limit_unit | string | — | Must be provided together with rate_limit_value. Values: 'rpm' (requests/min), 'rph' (requests/hour), or 'rpd' (requests/day). |
rate_limit_value | number | — | Must be provided together with rate_limit_unit. |
usage_limit_type | string | — | Type of usage limit: 'cost' (monetary) or 'tokens' (token count). Defaults to 'cost'. |
Parameters from the server's own tool schema.
An AI agent can call create_provider faster than any human can review — one bad instruction and it creates or modifies resources in Portkey Admin by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
Create a workspace provider backed by an org integration. The provider inherits the integration key, but its limits and expiration are enforced independently for that workspace. Returns the new provider id and slug. It is categorised as a Write tool in the Portkey Admin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_provider accepts 12 parameters: name, note, slug, expires_at, credit_limit, workspace_id, integration_id, periodic_reset, alert_threshold, rate_limit_unit, rate_limit_value, usage_limit_type. Required: name, integration_id. The full parameter table on this page comes from the server's own tool schema.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for create_provider: 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.
create_provider is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_provider 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 create_provider. 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.
create_provider 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.