Low Risk

fast_check

fast_check

How to control fast_check ↓

What fast_check does on urlDNA MCP Server

AI agents call fast_check to retrieve information from urlDNA MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why fast_check needs a policy

Given the urlDNA threat intelligence platform context where tools like 'get_scan', 'get_brand', and 'list_queries' are available, 'fast_check' most likely performs a query or lookup operation against the threat database. Without a description, confidence is reduced, but the naming pattern and server purpose indicate a read operation with no side effects.

From the tool's definition Tool name 'fast_check' paired with context of URL scanning and threat detection suggests information retrieval (likely a quick check/lookup operation). No description provided to confirm scope.

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

How to control fast_check

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 fast_check:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "fast_check": {}
  }
}

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

  1. Create a free account and register urlDNA MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about fast_check

What does the fast_check tool do? +

fast_check. 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 fast_check? +

Register the urlDNA MCP Server MCP server in PolicyLayer and add a rule for fast_check: 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 fast_check? +

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

Can I rate-limit fast_check? +

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

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

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

Free to start. No card required.

14 urlDNA MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.