get_api_details

THE RISK

Low Risk

Why get_api_details needs a policy

This tool retrieves and queries data (specifications, pricing information, authentication details, and usage examples) without creating, modifying, deleting, or executing operations. It has no side effects beyond informing the user about API capabilities. The blast radius of misuse is minimal—an agent querying details about APIs poses no direct risk to systems or data.

From the tool's definition Tool name 'get_api_details' and description 'Full specs, pricing, auth, and usage examples for a specific API' indicate retrieval of informational metadata about APIs. No modification, deletion, code execution, or financial transactions occur.

Documented attack patterns abuse exactly the kind of access get_api_details gives an agent:

POLICY

How to control get_api_details

PolicyLayer is an MCP gateway — it sits between your AI agents and APIClaw, and nothing reaches the server without passing your rules. This is the rule we recommend for get_api_details:

policy.json

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

get_api_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register APIClaw — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More APIClaw tools

Financial setup_metered_billing Set up pay-per-call billing. Creates a subscription that charges $0.002 per API call at en Execute call_api Execute a callable API through APIClaw Execute capability Run a job-to-be-done by capability name (currency_convert, web_search, tts, transcribe, sc Execute start_mission Start a Control Plane mission — a structured, observable orchestration that runs on APICla Execute resume_chain Resume a paused or partially-executed chain by id. Write verify_code Verify the 6-digit code sent to your email after register_owner. This completes registrati Write register_owner LEGACY auth path (kept for back-compat). The canonical agent-native flow is Write remind_owner Send a reminder email to verify workspace ownership (if verification is pending).

All 24 APIClaw tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_api_details

What does the get_api_details tool do? +

Full specs, pricing, auth, and usage examples for a specific API. It is categorised as a Read tool in the APIClaw MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_api_details? +

Register the APIClaw MCP server in PolicyLayer and add a rule for get_api_details: 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 APIClaw. Nothing to install.

What risk level is get_api_details? +

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

Can I rate-limit get_api_details? +

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

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

get_api_details is provided by the APIClaw MCP server (nordsym/apiclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every APIClaw tool call.

Start from APIClaw, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →