credentials_set
Store or update a credential. Encrypts the value with AES-256-GCM and saves to ~/.aibtc/credentials.enc. If the service/key pair already exists, it is updated.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/credentials-set.md
What credentials_set does on Aibtc
AI agents use credentials_set to create or update resources in Aibtc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aibtc environment.
Why credentials_set is rated Medium
The tool performs a Write operation—it creates new credentials or modifies existing ones in an encrypted file. While it modifies sensitive authentication data, the action is reversible (credentials can be updated again or removed). It does not delete/destroy data (not Destructive), does not move money (not Financial), and does not execute arbitrary code (not Execute).
From the tool's definition Tool description states: 'Store or update a credential' and 'saves to ~/.aibtc/credentials.enc. If the service/key pair already exists, it is updated.' This is a reversible modification operation that creates or updates stored credential data.
Attacks that exploit this kind of access
The rule that runs credentials_set safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For credentials_set, this is the rule to start with:
credentials_set 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 Aibtc, apply this rule, and every credentials_set call is checked against it from then on.
Questions about credentials_set
Store or update a credential. Encrypts the value with AES-256-GCM and saves to ~/.aibtc/credentials.enc. If the service/key pair already exists, it is updated. It is categorised as a Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aibtc MCP server in PolicyLayer and add a rule for credentials_set: 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 Aibtc. Nothing to install.
credentials_set 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 credentials_set 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 credentials_set. 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.
credentials_set is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue