set_provider_key
Register a BYOK provider API key (encrypted at rest, BYOK plan only). Jobs whose model belongs to this provider then run on YOUR key and charge 0 credits. Providers: openai, gemini, anthropic, fal, elevenlabs, minimax.
This record as markdown: /tools/com-framesail-framesail/set-provider-key.md
What set_provider_key does on Framesail
AI agents use set_provider_key to create or update resources in Framesail, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Framesail environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | Yes | The provider API key to register; stored encrypted at rest |
provider | string | Yes | Provider the key belongs to: "openai", "gemini", "anthropic", "fal", "elevenlabs", or "minimax" |
Parameters from the server's own tool schema.
Why set_provider_key is rated Medium
The tool creates/registers API credentials that irreversibly change how the system routes requests and charges costs. This is Write (creates/modifies configuration data) rather than Financial because the tool itself does not move money—it configures a billing mechanism.
From the tool's definition Tool name and description: 'Register a BYOK provider API key' and 'Jobs whose model belongs to this provider then run on YOUR key and charge 0 credits.' This creates and stores a credential that modifies billing and service routing.
Attacks that exploit this kind of access
The rule that runs set_provider_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Framesail, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_provider_key, this is the rule to start with:
set_provider_key stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Framesail, apply this rule, and every set_provider_key call is checked against it from then on.
Questions about set_provider_key
Register a BYOK provider API key (encrypted at rest, BYOK plan only). Jobs whose model belongs to this provider then run on YOUR key and charge 0 credits. Providers: openai, gemini, anthropic, fal, elevenlabs, minimax. It is categorised as a Write tool in the Framesail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
set_provider_key accepts 2 parameters: key, provider. Required: key, provider. The full parameter table on this page comes from the server's own tool schema.
Register the Framesail MCP server in PolicyLayer and add a rule for set_provider_key: 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 Framesail. Nothing to install.
set_provider_key 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 set_provider_key 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 set_provider_key. 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.
set_provider_key is provided by the Framesail MCP server (https://api.framesail.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Framesail, and thousands of servers like it.
This server
Across the catalogue