search
Search 1inch documentation and API reference
This record as markdown: /tools/com-1inch-business-mcp/search.md
What search does on 1inch MCP
AI agents call search 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 |
|---|---|---|---|
page | number | — | Page number for pagination (default 1) |
limit | number | — | Maximum results per collection (default 10) |
query | string | Yes | Search query string |
include_body | boolean | — | Include full document body in results (default true). Set to false for smaller responses. |
Parameters from the server's own tool schema.
Why search is rated Low
The tool retrieves and queries existing documentation and API reference materials without side effects. This is a standard read operation with minimal risk—it only returns information already publicly available. Even in the context of a financial platform (1inch is a DEX aggregator), searching documentation cannot directly move funds, execute trades, or cause irreversible changes.
From the tool's definition Tool searches documentation and API reference; described as 'Search 1inch documentation' with no capability to modify, delete, or execute operations. Pure information retrieval.
Attacks that exploit this kind of access
The rule that runs search 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 search, this is the rule to start with:
search 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 search call is checked against it from then on.
Questions about search
Search 1inch documentation and API reference. It is categorised as a Read tool in the 1inch MCP MCP Server, which means it retrieves data without modifying state.
search accepts 4 parameters: page, limit, query, include_body. Required: query. 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 search: 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.
search 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 search 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 search. 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.
search 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