Revoke an API key for the authenticated agent store (requires ONELY_API_KEY).
AI agents call 1ly_revoke_key to permanently remove resources in 1ly — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes |
Parameters from the server's own tool schema.
Revoking an API key permanently destroys authentication credentials, cutting off all access that relied on that key. This is an irreversible destructive action with high blast radius since misuse could lock out legitimate agents or services from the store's APIs.
From the tool's definition Revoke an API key — revoking an API key is an irreversible action that permanently invalidates access credentials, which cannot be undone.
Documented attack patterns abuse exactly the kind of access 1ly_revoke_key gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and 1ly, and nothing reaches the server without passing your rules. This is the rule we recommend for 1ly_revoke_key:
{
"version": "1",
"default": "deny",
"hide": [
"1ly_revoke_key"
]
} 1ly_revoke_key disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Revoke an API key for the authenticated agent store (requires ONELY_API_KEY). It is categorised as a Destructive tool in the 1ly MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
1ly_revoke_key accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the 1ly MCP server in PolicyLayer and add a rule for 1ly_revoke_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 1ly. Nothing to install.
1ly_revoke_key is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the 1ly_revoke_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 1ly_revoke_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.
1ly_revoke_key is provided by the 1ly MCP server (@1ly/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from 1ly, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 1ly tools catalogued and risk-classified — across an index of 43,000+ MCP servers.