create_api_key
Create a new API key. Returns the raw key once \u2014 store it securely. Requires paid subscription.
This record as markdown: /tools/app-businys-mcp-server/create-api-key.md
What create_api_key does on Businys
AI agents use create_api_key to create or update resources in Businys, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Businys environment.
Why create_api_key is rated Medium
This tool creates credentials that grant access to APIs, making it a Write operation (creates new data with side effects). The severity is high because: (1) API keys are sensitive authentication tokens that could be exfiltrated if mishandled by an agent, (2) misuse could grant unauthorized access to user accounts, (3) creation of keys is reversible but credential leakage is very difficult to contain.
From the tool's definition 'Create a new API key' - generates a new credential that modifies the authentication/authorization state. Returns sensitive 'raw key' that must be 'stored securely', indicating high-value secret material that enables programmatic access to the system.
Attacks that exploit this kind of access
The rule that runs create_api_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_api_key, this is the rule to start with:
create_api_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 Businys, apply this rule, and every create_api_key call is checked against it from then on.
Questions about create_api_key
Create a new API key. Returns the raw key once \u2014 store it securely. Requires paid subscription. It is categorised as a Write tool in the Businys MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Businys MCP server in PolicyLayer and add a rule for create_api_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 Businys. Nothing to install.
create_api_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 create_api_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 create_api_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.
create_api_key is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
This server
Across the catalogue