tool_safe_http_probe_workflow

WHAT IT DOES

What tool_safe_http_probe_workflow does on ScopePilot MCP

AI agents invoke tool_safe_http_probe_workflow to trigger actions in ScopePilot MCP. 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 tool_safe_http_probe_workflow needs a policy

Based on the tool name, 'http_probe_workflow' implies actively sending HTTP probes/requests to external web targets, which constitutes executing external operations. The server context of 'authorized web security testing' and sibling tools (crawl, CORS observation, header checking, recon) all involve active network operations against targets.

From the tool's definition Tool name contains 'http_probe_workflow', suggesting it sends HTTP requests to external targets. Description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tool_safe_http_probe_workflow Rate-limited

tool_safe_http_probe_workflow 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": {
    "tool_safe_http_probe_workflow": {
      "limits": [
        {
          "counter": "tool_safe_http_probe_workflow_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 ScopePilot MCP, so you can run agents against it safely.

FAQ

Questions about tool_safe_http_probe_workflow

What does the tool_safe_http_probe_workflow tool do? +

tool_safe_http_probe_workflow. It is categorised as a Execute tool in the ScopePilot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on tool_safe_http_probe_workflow? +

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

What risk level is tool_safe_http_probe_workflow? +

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

Can I rate-limit tool_safe_http_probe_workflow? +

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

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

tool_safe_http_probe_workflow is provided by the ScopePilot MCP server (rens1215/scopepilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.