Medium Risk

intel_http

Makes a live HEAD request to the target domain from the Cloudflare edge, follows up to 5 redirects, and returns the full redirect chain, final HTTP status, key response headers, a security header score, and any third-party surveillance actors referenced in the Content-Security-Policy header. Use ...

Part of the TunnelMind Data API server.

intel_http can modify TunnelMind Data API data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE TUNNELMIND DATA API →

Free to start. No card required.

AI agents use intel_http to create or modify resources in TunnelMind Data API. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call intel_http repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach TunnelMind Data API.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "intel_http": {
      "limits": [
        {
          "counter": "intel_http_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full TunnelMind Data API policy for all 54 tools.

Get this rule live on your own TunnelMind Data API server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TUNNELMIND DATA API →

View all 54 tools →

These attack patterns abuse exactly the kind of access intel_http gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so intel_http only ever does what you allow.

SECURE TUNNELMIND DATA API →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the intel_http tool do? +

Makes a live HEAD request to the target domain from the Cloudflare edge, follows up to 5 redirects, and returns the full redirect chain, final HTTP status, key response headers, a security header score, and any third-party surveillance actors referenced in the Content-Security-Policy header. Use this tool when: - You want to verify whether a site enforces HTTPS and HSTS. - You need to inspect what third-party scripts a site loads via its CSP header. - You are assessing a domain's security posture before trusting it. - You want to detect surveillance actors embedded in a site's CSP. Do NOT use this tool when: - You need tracker database data (category, score, entity) — use get_domain instead. - You need the technology stack (CMS, framework) — use intel_stack instead. - You need robots.txt AI crawler policy — use intel_robots instead. Inputs: - domain (query, required): Domain to probe. Can include or omit https://. Examples: nytimes.com, https://example.com. Returns: - reachable: false if the domain did not respond within 6 seconds. - redirect_chain: each hop with URL, status code, and Location header. - security_headers.score: 0-100 based on presence of HSTS, CSP, X-Content-Type, X-Frame-Options, Referrer-Policy. - security_headers.missing: list of headers absent. - csp_actors: known surveillance actors detected in the CSP header. - error: set if the connection failed. Cost: - Free. No API key required. Latency: - Typical: 1-3s (outbound fetch), p99: 6s (timeout). Plan for async if chaining calls.. It is categorised as a Write tool in the TunnelMind Data API MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on intel_http? +

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

What risk level is intel_http? +

intel_http is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit intel_http? +

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

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

intel_http is provided by the TunnelMind Data API MCP server (https://mcp-data.tunnelmind.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every TunnelMind Data API tool call.

Deterministic rules across all 54 TunnelMind Data API tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.