bruno_run_collection · Bruno MCP Server MCP: Risk & Policy

WHAT IT DOES

What bruno_run_collection does on Bruno MCP Server

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

This tool executes a set of API requests whose effects depend entirely on what those requests do. While the tool itself is not destructive or financial by nature, it triggers external operations (API calls) with potentially significant side effects (creating resources, modifying data, triggering workflows).

From the tool's definition Tool description states it will 'run all requests in a Bruno collection or specific folder'. Running API requests is an execute operation with effects determined by the collection contents and external APIs being called.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bruno_run_collection Rate-limited

bruno_run_collection 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": {
    "bruno_run_collection": {
      "limits": [
        {
          "counter": "bruno_run_collection_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 Bruno MCP Server, so you can run agents against it safely.

FAQ

Questions about bruno_run_collection

What does the bruno_run_collection tool do? +

Run all requests in a Bruno collection or specific folder. It is categorised as a Execute tool in the Bruno MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on bruno_run_collection? +

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

What risk level is bruno_run_collection? +

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

Can I rate-limit bruno_run_collection? +

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

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

bruno_run_collection is provided by the Bruno MCP Server MCP server (jcr82/bruno-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.