apitap_search

THE RISK

Low Risk

Why apitap_search needs a policy

This tool performs a search operation to discover and retrieve metadata about existing API endpoints. It has no side effects—it only queries and returns information. No data is created, modified, deleted, or executed. This is a classic Read operation (search, list, fetch pattern).

From the tool's definition Tool name 'apitap_search' combined with description 'Find captured API endpoints by domain or keyword' indicates a search/query operation that retrieves information about pre-captured endpoints without modifying or executing them.

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

POLICY

How to control apitap_search

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

policy.json

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

apitap_search 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 ApiTap — 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 ApiTap tools

Execute apitap_capture_start Start an interactive capture session. Launches browser, begins capturing API traffic. Execute apitap_auth_request Open a visible browser for human login (handles 2FA, CAPTCHAs). Execute apitap_capture Launch a browser to capture a site\ Execute apitap_capture_interact Drive a live capture session browser. Execute apitap_replay Call a captured API endpoint and return live data. Execute apitap_replay_batch Replay multiple captured endpoints in parallel across domains. Write apitap_capture_finish Finish a capture session: verifies endpoints and writes skill files. Read apitap_browse Get data from a URL in one call: checks skill files, runs discovery, replays best endpoint

All 12 ApiTap 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 apitap_search

What does the apitap_search tool do? +

Find captured API endpoints by domain or keyword. It is categorised as a Read tool in the ApiTap MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on apitap_search? +

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

What risk level is apitap_search? +

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

Can I rate-limit apitap_search? +

Yes. Add a rate_limit block to the apitap_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.

How do I block apitap_search completely? +

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

What MCP server provides apitap_search? +

apitap_search is provided by the ApiTap MCP server (n1byn1kt/apitap). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ApiTap tool call.

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

CHECK YOUR STACK →