This record as markdown: /tools/io-github-1lystore-mcp-server/1ly-delete-link.md
What 1ly_delete_link does on 1ly
AI agents call 1ly_delete_link 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.
Why 1ly_delete_link is rated Critical
The tool performs a permanent deletion action ('Delete an API link by id'). Deletion of API links is irreversible and cannot be undone, making this a Destructive action rather than merely Write. The high severity reflects that an AI agent given this tool could accidentally or maliciously remove important API infrastructure.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete an API link by id'. This is an irreversible operation that removes data.
Attacks that exploit this kind of access
The rule that runs 1ly_delete_link 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_delete_link, this is the rule to start with:
1ly_delete_link is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect 1ly, apply this rule, and every 1ly_delete_link call is checked against it from then on.
Questions about 1ly_delete_link
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.
Register the 1ly MCP server in PolicyLayer and add a rule for 1ly_delete_link: 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_delete_link 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_delete_link 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_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.
1ly_delete_link 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.
More on 1ly, and thousands of servers like it.
Across the catalogue