update_vendor · Wedding Planner MCP Server MCP

WHAT IT DOES

What update_vendor does on Wedding Planner MCP Server

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

WHY IT NEEDS A POLICY

Why update_vendor needs a policy

This tool modifies vendor information reversibly within the Google Sheets template. It is clearly a Write operation (updates existing records) rather than Read (retrieves data), Execute (runs external code), Destructive (deletes data), or Financial (moves money).

From the tool's definition Tool name 'update_vendor' and description 'Update a vendor by row number' indicate modification of existing data in the wedding planner spreadsheet without deletion or financial transaction.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_vendor Rate-limited

update_vendor 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_vendor": {
      "limits": [
        {
          "counter": "update_vendor_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 Wedding Planner MCP Server, so you can run agents against it safely.

FAQ

Questions about update_vendor

What does the update_vendor tool do? +

Update a vendor by row number. It is categorised as a Write tool in the Wedding Planner 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_vendor? +

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

What risk level is update_vendor? +

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

Can I rate-limit update_vendor? +

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

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

update_vendor is provided by the Wedding Planner MCP Server MCP server (kiboud/weddingplanner_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.