Medium Risk

create_request

Generate .bru request files for API testing

How to control create_request ↓

What create_request does on Bruno MCP Server

AI agents use create_request to create or update resources in Bruno MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bruno MCP Server environment.

Medium Risk

Why create_request needs a policy

This tool creates new request files (.bru format) for API testing collections. File creation is a reversible write operation — files can be deleted or modified later. It does not execute API calls, delete data irreversibly, or move money.

From the tool's definition Tool description states 'Generate .bru request files' — this creates new files in the Bruno API testing collection, which is a write operation that modifies the file system and collection structure.

Documented attack patterns abuse exactly the kind of access create_request gives an agent:

How to control create_request

PolicyLayer is an MCP gateway — it sits between your AI agents and Bruno MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_request:

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

create_request stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Bruno MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about create_request

What does the create_request tool do? +

Generate .bru request files for API testing. It is categorised as a Write tool in the Bruno MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_request? +

Register the Bruno MCP Server MCP server in PolicyLayer and add a rule for create_request: 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 create_request? +

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

Can I rate-limit create_request? +

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

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

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

Enforce policy on every Bruno MCP Server tool call.

Start from Bruno MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

8 Bruno MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.