update_request · Postman MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_request does on Postman MCP Server

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

WHY IT NEEDS A POLICY

Why update_request needs a policy

The tool modifies existing request metadata/configuration in Postman collections (headers, body, URL, parameters, etc.) but does not delete data or execute external operations. This is a standard Write operation. Severity is medium because misconfigured requests could cause unintended API calls to production systems, but the changes are reversible and localized to Postman configuration.

From the tool's definition Tool description states 'Update an existing API request in a Postman collection' — updates are reversible modifications of data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_request Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_request": {
      "limits": [
        {
          "counter": "update_request_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 Postman MCP Server, so you can run agents against it safely.

FAQ

Questions about update_request

What does the update_request tool do? +

Update an existing API request in a Postman collection. It is categorised as a Write tool in the Postman 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 update_request? +

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

What risk level is update_request? +

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

Can I rate-limit update_request? +

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

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

update_request is provided by the Postman MCP Server MCP server (sondang91/postman-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.