// MCP TOOL REFERENCE

1ly_revoke_key

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

Part of the 1ly MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents may call 1ly_revoke_key to permanently remove or destroy resources in 1ly. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

// WHY ENFORCE A POLICY ON 1LY_REVOKE_KEY

Without a policy, an AI agent could call 1ly_revoke_key in a loop, permanently destroying resources in 1ly. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

// RECOMMENDED POLICY

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

io-github-1lystore-mcp-server.yaml

tools:
  1ly_revoke_key:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full 1ly policy for all 23 tools.

// DETAILS

Tool Name 1ly_revoke_key

Category Destructive

MCP Server 1ly MCP Server

Risk Level Critical

// MORE 1LY TOOLS

Financial 1ly_withdraw Destructive 1ly_delete_link Execute 1ly_launch_token Write 1ly_create_key Write 1ly_create_link Write 1ly_create_store Write 1ly_update_avatar Write 1ly_update_link

View all 23 tools →

// WHAT CAN GO WRONG

Agents calling destructive-class tools like 1ly_revoke_key have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER DESTRUCTIVE TOOLS ACROSS MCP SERVERS

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

AbraFlexi contact_delete AbraFlexi evidence_delete AbraFlexi invoice_issued_delete AbraFlexi product_delete ACR — Agent Composition Records acknowledge_threat AdButler campaign_bulk_delete_catalog_ad_items

// IN CONTEXT OF CRITICAL RISK

1ly_revoke_key is one of the critical-risk operations in 1ly. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

// RELATED READING

// FAQ

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? +

Add a rule in your Intercept YAML policy under the tools section for 1ly_revoke_key. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the 1ly MCP server.

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 Intercept 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 Intercept 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). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

1ly_revoke_key

Let agents act without letting them run wild.