1ly_list_withdrawals

List withdrawal requests for your store (requires ONELY_API_KEY).

SERVER1ly SOURCE@1ly/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-1lystore-mcp-server/1ly-list-withdrawals.md

WHAT IT DOES

What 1ly_list_withdrawals does on 1ly

AI agents call 1ly_list_withdrawals to retrieve information from 1ly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why 1ly_list_withdrawals is rated Low

This tool retrieves historical withdrawal request data from the user's store without modifying, deleting, or executing any operations. The verb 'list' is a read-only action. While the context involves financial operations (a crypto/token trading platform), the tool itself only reads withdrawal records.

From the tool's definition Tool name '1ly_list_withdrawals' and description 'List withdrawal requests for your store' indicate a query/retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs 1ly_list_withdrawals 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_list_withdrawals, this is the rule to start with:

1ly_list_withdrawals Allowed

1ly_list_withdrawals is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "1ly_list_withdrawals": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 1ly, apply this rule, and every 1ly_list_withdrawals call is checked against it from then on.

FAQ

Questions about 1ly_list_withdrawals

What does the 1ly_list_withdrawals tool do? +

List withdrawal requests for your store (requires ONELY_API_KEY). It is categorised as a Read tool in the 1ly MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on 1ly_list_withdrawals? +

Register the 1ly MCP server in PolicyLayer and add a rule for 1ly_list_withdrawals: 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.

What risk level is 1ly_list_withdrawals? +

1ly_list_withdrawals is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit 1ly_list_withdrawals? +

Yes. Add a rate_limit block to the 1ly_list_withdrawals 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.

How do I block 1ly_list_withdrawals completely? +

Set action: deny in the PolicyLayer policy for 1ly_list_withdrawals. 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.

What MCP server provides 1ly_list_withdrawals? +

1ly_list_withdrawals 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.

KEEP EXPLORING

More on 1ly, and thousands of servers like it.

This server

All 24 1ly tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →