1ly

23 tools. 11 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated:

11 can modify or destroy data
12 read-only
23 tools total
Read (12) Write / Execute (8) Destructive / Financial (3)

Financial operations (1ly_withdraw) can move real money. An agent caught in a loop could drain accounts before anyone notices.

Destructive tools (1ly_delete_link, 1ly_revoke_key) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (1ly_create_key, 1ly_create_link, 1ly_create_store) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (1ly_launch_token) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

Block financial tools by default
1ly_withdraw:
  rules:
    - action: deny

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations
1ly_delete_link:
  rules:
    - action: deny

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
1ly_create_key:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
1ly_call:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Can an AI agent move money through the 1ly MCP server? +

Yes. The 1ly server exposes 1 financial tools including 1ly_withdraw. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. Intercept lets you block financial tools by default or set per-tool rate limits.

Can an AI agent delete data through the 1ly MCP server? +

Yes. The 1ly server exposes 2 destructive tools including 1ly_delete_link, 1ly_revoke_key. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through 1ly? +

The 1ly server has 7 write tools including 1ly_create_key, 1ly_create_link, 1ly_create_store. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the 1ly MCP server expose? +

23 tools across 5 categories: Destructive, Execute, Financial, Read, Write. 12 are read-only. 11 can modify, create, or delete data.

How do I add Intercept to my 1ly setup? +

One line change. Instead of running the 1ly server directly, prefix it with Intercept: intercept -c io-github-1lystore-mcp-server.yaml -- npx -y @@1ly/mcp-server. Download a pre-built policy from policylayer.com/policies/io-github-1lystore-mcp-server and adjust the limits to match your use case.

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

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.