Critical Risk →

1ly_delete_link

Delete an API link by id (requires ONELY_API_KEY).

Single-target operation

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

@1ly/mcp-server Destructive

AI agents may call 1ly_delete_link 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.

Without a policy, an AI agent could call 1ly_delete_link 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.

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

io-github-1lystore-mcp-server.yaml
tools:
  1ly_delete_link:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full 1ly policy for all 23 tools.

Tool Name 1ly_delete_link
Category Destructive
MCP Server 1ly MCP Server
Risk Level Critical

View all 23 tools →

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

Browse the full MCP Attack Database →

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

1ly_delete_link 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.

What does the 1ly_delete_link tool do? +

Delete an API link by id (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_delete_link? +

Add a rule in your Intercept YAML policy under the tools section for 1ly_delete_link. 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_delete_link? +

1ly_delete_link 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_delete_link? +

Yes. Add a rate_limit block to the 1ly_delete_link 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_delete_link completely? +

Set action: deny in the Intercept policy for 1ly_delete_link. 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_delete_link? +

1ly_delete_link 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.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.