search_docs

THE RISK

Low Risk

Why search_docs needs a policy

This tool retrieves and searches documentation without modifying any data or triggering external actions. It is a pure information retrieval operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'search_docs' and description 'Search the official urlDNA documentation' indicate a retrieval operation with no side effects. The action is querying documentation content.

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

POLICY

How to control search_docs

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

policy.json

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

search_docs 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 urlDNA MCP Server — 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 urlDNA MCP Server tools

Destructive delete_query delete_query Execute new_scan new_scan Write create_query create_query Write update_query update_query Read brand_scans brand_scans Read fast_check fast_check Read get_brand get_brand Read get_query get_query

All 14 urlDNA MCP Server 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 search_docs

What does the search_docs tool do? +

Search the official urlDNA documentation for integrations, API usage, and guides. It is categorised as a Read tool in the urlDNA MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_docs? +

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

What risk level is search_docs? +

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

Can I rate-limit search_docs? +

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

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

search_docs is provided by the urlDNA MCP Server MCP server (urldna/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every urlDNA MCP Server tool call.

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

CHECK YOUR STACK →