update_vendors · Wpm Mcp Server MCP: Risk & Policy

WHAT IT DOES

What update_vendors does on Wpm Mcp Server

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

WHY IT NEEDS A POLICY

Why update_vendors needs a policy

This tool modifies existing vendor data reversibly. It is a Write operation rather than Read (retrieves data), Execute (runs code/scripts), Destructive (irreversibly deletes), or Financial (moves money). Update operations can typically be rolled back or corrected. Severity is medium because vendor data updates could affect business operations and vendor relationships, but the impact is generally recoverable.

From the tool's definition Tool name 'update_vendors' and description 'Updates a vendor' indicate data modification. The description is truncated but clearly indicates an update operation on vendor records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_vendors Rate-limited

update_vendors 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_vendors": {
      "limits": [
        {
          "counter": "update_vendors_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 Wpm Mcp Server, so you can run agents against it safely.

FAQ

Questions about update_vendors

What does the update_vendors tool do? +

Updates a vendor.\r\n \r\n\r\n<strong>NOTE:</strong> Any field not included in the update request will be set to either an empty string or. It is categorised as a Write tool in the Wpm 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_vendors? +

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

What risk level is update_vendors? +

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

Can I rate-limit update_vendors? +

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

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

update_vendors is provided by the Wpm Mcp Server MCP server (wpm-mcp-server-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.