AI agents call keychain_status to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
platform | string | — | Platform ID to check. Omit to return all connected platforms. |
Parameters from the server's own tool schema.
This tool retrieves status information about stored credentials without executing any actions, modifying data, or triggering external operations. It is a read-only inspection capability. The low severity reflects minimal blast radius—an agent could at most discover which credentials are connected, but cannot authenticate, modify, or execute with those credentials.
From the tool's definition Tool name 'keychain_status' and description 'Check the connection status of one or all platform credentials' indicate a query/check operation with no modification or execution of credentials or external systems.
Attacks that exploit this kind of access
Check the connection status of one or all platform credentials stored in the UnClick Keychain for the current UNCLICK_API_KEY. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
keychain_status accepts 1 parameter: platform. 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_status: 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_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the keychain_status 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_status. 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_status 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →