set_request_base · Req MCP: Risk & Policy

WHAT IT DOES

What set_request_base does on Req

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

WHY IT NEEDS A POLICY

Why set_request_base needs a policy

This tool creates or modifies configuration data (the base URL) in a reversible manner. It does not retrieve data (Read), execute arbitrary code or commands (Execute), delete data (Destructive), or move money (Financial). The blast radius is low because misconfiguration of a base URL affects only the scope of future HTTP requests made by the user/agent, and can be easily corrected by calling the tool again.

From the tool's definition Tool description states it 'Sets the base URL used for future Request API calls' — this modifies configuration state that affects subsequent operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_request_base Rate-limited

set_request_base 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_request_base": {
      "limits": [
        {
          "counter": "set_request_base_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about set_request_base

What does the set_request_base tool do? +

Sets the base URL used for future Request API calls. It is categorised as a Write tool in the Req MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_request_base? +

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

What risk level is set_request_base? +

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

Can I rate-limit set_request_base? +

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

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

set_request_base is provided by the Req MCP server (tarminarx/request-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.