keychain_secure_connect

SERVERUnClick SOURCE@unclick/mcp-server

Medium RISK CLASS

Category Write

Parameters 31 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/keychain-secure-connect.md

WHAT IT DOES

What keychain_secure_connect does on UnClick

AI agents use keychain_secure_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, stripe, openai, vercel, cloudflare, etc.
`setup_url`	string	—	Optional URL to the platform's API key settings page, shown on the input page.

Parameters from the server's own tool schema.

RISK

Why keychain_secure_connect is rated Medium

The tool creates or stores a credential connection, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. However, severity is high because misuse could lead to unauthorized credential storage or impersonation via the stored connection, affecting downstream actions.

From the tool's definition Tool description states it 'Securely connect a platform credential' and stores/establishes a connection that persists (requires two calls: first to get URL, second to 'complete the connection').

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs keychain_secure_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_secure_connect, this is the rule to start with:

keychain_secure_connect Rate-limited

keychain_secure_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "keychain_secure_connect": {
      "limits": [
        {
          "counter": "keychain_secure_connect_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every keychain_secure_connect call is checked against it from then on.

FAQ

Questions about keychain_secure_connect

What does the keychain_secure_connect tool do? +

Securely connect a platform credential without exposing the key in chat. Checks environment variables first; if not found, opens a localhost secure input page for the user to paste their key. Call once to get the URL, then call again after the user submits to complete the connection. 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.

What parameters does keychain_secure_connect accept? +

keychain_secure_connect accepts 3 parameters: label, platform, setup_url. Required: platform. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on keychain_secure_connect? +

Register the UnClick MCP server in PolicyLayer and add a rule for keychain_secure_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.

What risk level is keychain_secure_connect? +

keychain_secure_connect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit keychain_secure_connect? +

Yes. Add a rate_limit block to the keychain_secure_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.

How do I block keychain_secure_connect completely? +

Set action: deny in the PolicyLayer policy for keychain_secure_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.

What MCP server provides keychain_secure_connect? +

keychain_secure_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.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

connect-gmail on Meme MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →