keychain_connect
Store an encrypted platform credential in the UnClick Keychain. Tests the credential against the platform API before saving. Scoped to the caller's UNCLICK_API_KEY.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/keychain-connect.md
What keychain_connect does on UnClick
AI agents use keychain_connect to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
label | string | — | Optional label to distinguish multiple credentials for the same platform (default: 'default'). |
platform | string | Yes | Platform ID: github, supabase, vercel, stripe, cloudflare. |
credential | string | Yes | API key or token for the platform. |
Parameters from the server's own tool schema.
Why keychain_connect is rated Medium
This tool creates and stores encrypted credentials in a keychain system. While the action itself is reversible (credentials can be updated or removed), the severity is elevated to 'high' because improper use could result in compromised credentials being stored, which could later enable unauthorized access to external platforms.
From the tool's definition Tool description states 'Store an encrypted platform credential in the UnClick Keychain', which is a create/modify operation that persists data. The credential storage is reversible and does not irreversibly delete data or move money.
Attacks that exploit this kind of access
The rule that runs keychain_connect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For keychain_connect, this is the rule to start with:
keychain_connect 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 UnClick, apply this rule, and every keychain_connect call is checked against it from then on.
Questions about keychain_connect
Store an encrypted platform credential in the UnClick Keychain. Tests the credential against the platform API before saving. Scoped to the caller's UNCLICK_API_KEY. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
keychain_connect accepts 3 parameters: label, platform, credential. Required: platform, credential. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for keychain_connect: 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 UnClick. Nothing to install.
keychain_connect 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 keychain_connect 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 keychain_connect. 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.
keychain_connect is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue