1ly_create_store
Create a new store for your agent on 1ly using wallet signature.Returns store + API key.
This record as markdown: /tools/io-github-1lystore-mcp-server/1ly-create-store.md
What 1ly_create_store does on 1ly
AI agents use 1ly_create_store 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_create_store is rated Medium
This tool creates a new store resource tied to a wallet, which is a Write operation (reversible state change). Severity is high because: (1) it generates API credentials that could be misused if an agent creates stores maliciously or excessively, (2) it ties to financial infrastructure (1ly.store for buying/selling APIs and launching tokens with USDC), and (3) unauthorized store creation could facilitate fraud or…
From the tool's definition Tool description explicitly states 'Create a new store' — a creation action that modifies data reversibly. Returns 'store + API key', indicating persistent resource creation.
Attacks that exploit this kind of access
The rule that runs 1ly_create_store 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_create_store, this is the rule to start with:
1ly_create_store 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_create_store call is checked against it from then on.
Questions about 1ly_create_store
Create a new store for your agent on 1ly using wallet signature.Returns store + 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_create_store: 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_create_store 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_create_store 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_create_store. 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_create_store 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