1ly_revoke_key

Revoke an API key for the authenticated agent store (requires ONELY_API_KEY).

SERVER1ly SOURCE@1ly/mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-1lystore-mcp-server/1ly-revoke-key.md

WHAT IT DOES

What 1ly_revoke_key does on 1ly

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.

RISK

Why 1ly_revoke_key is rated Critical

Revoking an API key cannot be undone; the key is permanently invalidated. This is an irreversible destructive action with high blast radius since misuse would disable authenticated access to the store's APIs for any agent or service relying on that key.

From the tool's definition Revoke an API key — revoking an API key is an irreversible action that permanently invalidates the key, preventing any future use.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs 1ly_revoke_key safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 1ly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For 1ly_revoke_key, this is the rule to start with:

1ly_revoke_key Hidden

1ly_revoke_key is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "1ly_revoke_key"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about 1ly_revoke_key

What does the 1ly_revoke_key tool do? +

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.

How do I enforce a policy on 1ly_revoke_key? +

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.

What risk level is 1ly_revoke_key? +

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.

Can I rate-limit 1ly_revoke_key? +

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.

How do I block 1ly_revoke_key completely? +

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.

What MCP server provides 1ly_revoke_key? +

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.

KEEP EXPLORING

More on 1ly, and thousands of servers like it.

This server

All 24 1ly tools → Critical-risk tools on this server →

Across the catalogue

web3_revoke_key on 0xarchive →deauthorize_ssh_key on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →