# 1ly_update_profile

Update basic store profile details (requires ONELY_API_KEY).

Agent View of the PolicyLayer registry record for `1ly_update_profile`. HTML page: https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-update-profile

## Facts

- Tool: `1ly_update_profile`
- Server: 1ly (`@1ly/mcp-server`) — https://policylayer.com/tools/io-github-1lystore-mcp-server.md
- Install: `npx -y @1ly/mcp-server`
- Homepage: https://github.com/1lystore/1ly-mcp-server
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "1ly_update_profile",
    "arguments": {}
  }
}
```

## Why 1ly_update_profile is rated Medium

The tool creates or modifies data (user profile details) without permanently deleting or overwriting it, placing it in the Write category. Severity is medium because unauthorized profile updates could allow an attacker to impersonate a store owner or mislead users, but the changes are reversible.

From the tool's own definition: "Tool name contains 'update', description says 'Update basic store profile details'. This modifies existing data (profile information) reversibly."

## Use case

AI agents use 1ly_update_profile to create or update resources in 1ly, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 1ly environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 1ly:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "1ly_update_profile": {
      "limits": [
        {
          "counter": "1ly_update_profile_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on 1ly (23)

- `1ly_delete_link` — Destructive — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-delete-link.md
- `1ly_revoke_key` — Destructive — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-revoke-key.md
- `1ly_call` — Financial — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-call.md
- `1ly_claim_fees` — Financial — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-claim-fees.md
- `1ly_launch_token` — Financial — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-launch-token.md
- `1ly_trade_token` — Financial — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-trade-token.md
- `1ly_withdraw` — Financial — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-withdraw.md
- `1ly_get_details` — Read — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-get-details.md
- `1ly_get_stats` — Read — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-get-stats.md
- `1ly_list_keys` — Read — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-list-keys.md
- `1ly_list_links` — Read — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-list-links.md
- `1ly_list_tokens` — Read — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-list-tokens.md
- `1ly_list_withdrawals` — Read — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-list-withdrawals.md
- `1ly_search` — Read — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-search.md
- `1ly_trade_quote` — Read — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-trade-quote.md
- `1ly_vault_status` — Read — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-vault-status.md
- `1ly_create_key` — Write — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-create-key.md
- `1ly_create_link` — Write — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-create-link.md
- `1ly_create_store` — Write — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-create-store.md
- `1ly_review` — Write — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-review.md
- `1ly_update_avatar` — Write — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-update-avatar.md
- `1ly_update_link` — Write — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-update-link.md
- `1ly_update_socials` — Write — https://policylayer.com/tools/io-github-1lystore-mcp-server/1ly-update-socials.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=io-github-1lystore-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-1lystore-mcp-server