cloud_intelligence · Bug Bounty Hunter MCP: Risk & Policy

WHAT IT DOES

What cloud_intelligence does on Bug Bounty Hunter MCP

AI agents invoke cloud_intelligence to trigger actions in Bug Bounty Hunter 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 cloud_intelligence needs a policy

Cloud asset discovery involves active scanning and enumeration of cloud infrastructure, while 'takeover analysis' implies testing for subdomain/cloud resource takeover vulnerabilities. This goes beyond passive reading — it actively probes external systems and may trigger or validate exploitable conditions.

From the tool's definition Performs Cloud Asset Discovery & Takeover analysis

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cloud_intelligence Rate-limited

cloud_intelligence 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": {
    "cloud_intelligence": {
      "limits": [
        {
          "counter": "cloud_intelligence_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 Bug Bounty Hunter MCP, so you can run agents against it safely.

FAQ

Questions about cloud_intelligence

What does the cloud_intelligence tool do? +

Performs Cloud Asset Discovery & Takeover analysis. It is categorised as a Execute tool in the Bug Bounty Hunter 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 cloud_intelligence? +

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

What risk level is cloud_intelligence? +

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

Can I rate-limit cloud_intelligence? +

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

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

cloud_intelligence is provided by the Bug Bounty Hunter MCP server (mauricioduarte100/bugbountymcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.