update_invitation_vendor · Wedding Planner MCP Server MCP

WHAT IT DOES

What update_invitation_vendor does on Wedding Planner MCP Server

AI agents use update_invitation_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_invitation_vendor needs a policy

This tool creates or modifies data reversibly within the Google Sheets wedding planner template. Updating vendor information (contact details, pricing, services, status) is a Write operation that can be undone or corrected. While it affects wedding planning decisions and vendor relationships, it does not irreversibly delete data (Destructive), execute external code (Execute), or move money (Financial).

From the tool's definition Tool name 'update_invitation_vendor' and description 'Update an invitation vendor by row number' indicate modification of existing data in the wedding planner spreadsheet.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_invitation_vendor Rate-limited

update_invitation_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_invitation_vendor": {
      "limits": [
        {
          "counter": "update_invitation_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_invitation_vendor

What does the update_invitation_vendor tool do? +

Update an invitation 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_invitation_vendor? +

Register the Wedding Planner MCP Server MCP server in PolicyLayer and add a rule for update_invitation_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_invitation_vendor? +

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

Can I rate-limit update_invitation_vendor? +

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

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

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