Low Risk

1ly_get_details

Get detailed information about a specific API on 1ly.store, including pricing, reviews, and payment info.

Accepts URL/endpoint input (endpoint); Single-target operation

Part of the 1ly MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call 1ly_get_details to retrieve information from 1ly without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though 1ly_get_details only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-1lystore-mcp-server.yaml
tools:
  1ly_get_details:
    rules:
      - action: allow

See the full 1ly policy for all 23 tools.

Tool Name 1ly_get_details
Category Read
MCP Server 1ly MCP Server
Risk Level Low

View all 23 tools →

What does the 1ly_get_details tool do? +

Get detailed information about a specific API on 1ly.store, including pricing, reviews, and payment info.. 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_get_details? +

Add a rule in your Intercept YAML policy under the tools section for 1ly_get_details. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the 1ly MCP server.

What risk level is 1ly_get_details? +

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

Can I rate-limit 1ly_get_details? +

Yes. Add a rate_limit block to the 1ly_get_details rule in your Intercept 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_get_details completely? +

Set action: deny in the Intercept policy for 1ly_get_details. 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_get_details? +

1ly_get_details is provided by the 1ly MCP server (@1ly/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on 1ly

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.