http_check · Keel MCP: Risk & Policy

WHAT IT DOES

What http_check does on Keel

AI agents invoke http_check to trigger actions in Keel. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why http_check needs a policy

Making HTTP requests is an active external operation that can trigger side effects on remote servers (e.g., hitting webhooks, APIs, or internal network endpoints). While it may appear read-like, it executes real network calls with potential SSRF implications and unintended side effects on targets, placing it in Execute rather than Read.

From the tool's definition 'Perform an HTTP request' — actively initiates outbound network requests to arbitrary URLs, triggering external operations whose effects depend on arguments

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

http_check Rate-limited

http_check stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "http_check": {
      "limits": [
        {
          "counter": "http_check_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Keel, so you can run agents against it safely.

FAQ

Questions about http_check

What does the http_check tool do? +

Perform an HTTP request and return timing breakdown. It is categorised as a Execute tool in the Keel MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on http_check? +

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

What risk level is http_check? +

http_check is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit http_check? +

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

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

http_check is provided by the Keel MCP server (seayniclabs/keel). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.