aqua
Query the 1inch Aqua API (v1.0) — analytics for Aqua strategies (shared-liquidity market making): maker stats, strategy lists, overview, activity, and volume series. Read-only. No OAuth required. REQUIRED: "action" — read actions (no OAuth): maker_stats, list_maker_strategies, strategy_overview, ...
This record as markdown: /tools/com-1inch-business-mcp/aqua.md
What aqua does on 1inch MCP
AI agents call aqua to retrieve information from 1inch MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
app | string | — | App contract address (strategy_* analytics actions). |
sort | string | — | Sort direction for list/activity/volume (asc|desc). |
limit | integer | Yes | Page size for list/activity/volume actions. |
maker | string | — | Maker EVM address (strategy_* analytics actions). |
action | string | Yes | Invalid or missing "action" parameter. Must be one of: "maker_stats", "list_maker_strategies", "strategy_overview", "strategy_activity", "strategy_volume", "lis |
cursor | string | — | Opaque pagination cursor from a previous response. |
status | array | Yes | Filter by lifecycle status for list_maker_strategies (e.g. ["open"]). |
address | string | — | Maker EVM address (maker_stats, list_maker_strategies). |
chainId | object | Yes | EVM chain ID (number) for single-strategy reads, or an array of chain IDs for list/stats filters. |
granularity | string | — | Volume series bucket (strategy_volume). |
strategyHash | string | — | Strategy hash (strategy_* analytics actions). |
Parameters from the server's own tool schema.
Why aqua is rated Low
This tool purely queries analytics data about 1inch Aqua strategies without performing any mutations, executions, or financial transactions. It retrieves maker statistics, strategy lists, activity logs, and volume data—all read-only operations with no side effects on blockchain state or user assets.
From the tool's definition Tool description explicitly states 'Read-only. No OAuth required.' and lists only read actions: 'maker_stats, list_maker_strategies, strategy_overview, strategy_activity, strategy_volume, list_opened.' No create, modify, delete, execute, or financial…
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs aqua safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1inch MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For aqua, this is the rule to start with:
aqua is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 1inch MCP, apply this rule, and every aqua call is checked against it from then on.
Questions about aqua
Query the 1inch Aqua API (v1.0) — analytics for Aqua strategies (shared-liquidity market making): maker stats, strategy lists, overview, activity, and volume series. Read-only. No OAuth required. REQUIRED: "action" — read actions (no OAuth): maker_stats, list_maker_strategies, strategy_overview, strategy_activity, strategy_volume, list_opened. Read the resource file://1inch-mcp/guides/aqua-workflow for per-action examples, priceRange semantics, and maker/taker flows. Raw HTTP: product_api with path "/aqua/v1.0/strategies/...". It is categorised as a Read tool in the 1inch MCP MCP Server, which means it retrieves data without modifying state.
aqua accepts 11 parameters: app, sort, limit, maker, action, cursor, status, address, chainId, granularity, strategyHash. Required: limit, action, status, chainId. The full parameter table on this page comes from the server's own tool schema.
Register the 1inch MCP server in PolicyLayer and add a rule for aqua: 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 1inch MCP. Nothing to install.
aqua is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the aqua 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 aqua. 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.
aqua is provided by the 1inch MCP server (https://api.1inch.com/mcp/protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1inch, and thousands of servers like it.
This server
Across the catalogue