1ly_update_profile
Update basic store profile details (requires ONELY_API_KEY).
This record as markdown: /tools/io-github-1lystore-mcp-server/1ly-update-profile.md
What 1ly_update_profile does on 1ly
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.
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 definition Tool name contains 'update', description says 'Update basic store profile details'. This modifies existing data (profile information) reversibly.
Attacks that exploit this kind of access
The rule that runs 1ly_update_profile 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_update_profile, this is the rule to start with:
1ly_update_profile stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 1ly, apply this rule, and every 1ly_update_profile call is checked against it from then on.
Questions about 1ly_update_profile
Update basic store profile details (requires ONELY_API_KEY). It is categorised as a Write tool in the 1ly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 1ly MCP server in PolicyLayer and add a rule for 1ly_update_profile: 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_update_profile is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the 1ly_update_profile 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_update_profile. 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_update_profile 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.
This server
Across the catalogue