New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

debug

[Requires authentication] Call the authenticate tool first to start or confirm 1inch Business login (initialize 200 is still anonymous). If authenticate or this tool returns HTTP 401, complete OAuth, then retry. Look up production API request logs for your 1inch Business organization to troublesh...

SERVER1inch MCP SOURCEhttps://api.1inch.com/mcp/protocol
Low RISK CLASS
Category Read
Parameters 50 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-1inch-business-mcp/debug.md

What debug does on 1inch MCP

AI agents call debug 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.

ParameterTypeRequiredDescription
limit number — Max log lines (max 100)
endTime string — RFC3339 end of query window. Defaults to now when omitted.
logLevel string — Filter by log level: "info", "warn", or "error". Omit to return all levels. Only applies to time-window mode (ignored when requestId is set).
requestId string — Production x-request-id (or correlation id) to find logs for. When set, searches JSON logs for this value scoped to your organization.
startTime string — RFC3339 start of query window. With requestId, defaults to 24h before endTime.

Parameters from the server's own tool schema.

Why debug is rated Low

Retrieves API logs for debugging; no data modification or execution occurs.

From the tool's definition Look up production API request logs to troubleshoot integration issues

Questions about debug

What does the debug tool do? +

[Requires authentication] Call the authenticate tool first to start or confirm 1inch Business login (initialize 200 is still anonymous). If authenticate or this tool returns HTTP 401, complete OAuth, then retry. Look up production API request logs for your 1inch Business organization to troubleshoot integration issues. Results are always scoped to your authenticated organization. Two modes: 1) By request id: pass requestId (the x-request-id header returned on 1inch API responses). Optionally narrow startTime/endTime (defaults: last 24 hours ending now). 2) Logs in a time window: omit requestId and pass both startTime and endTime (RFC3339). Optionally set logLevel ("info", "warn", or "error") to filter by severity; omit to return all levels. Limits: each call covers at most a 24-hour window; how far back you can query depends on your plan's log retention. It is categorised as a Read tool in the 1inch MCP MCP Server, which means it retrieves data without modifying state.

What parameters does debug accept? +

debug accepts 5 parameters: limit, endTime, logLevel, requestId, startTime. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on debug? +

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

What risk level is debug? +

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

Can I rate-limit debug? +

Yes. Add a rate_limit block to the debug 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 debug completely? +

Set action: deny in the PolicyLayer policy for debug. 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 debug? +

debug 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 1inch's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.