add_vendor · Wedding Planner MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_vendor does on Wedding Planner MCP Server

AI agents use add_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 add_vendor needs a policy

This tool creates a new record (vendor entry) in a spreadsheet in a reversible manner. It modifies data by adding a row to the Vendors sheet, which is the definition of Write category. The operation is non-destructive and has minimal blast radius — an erroneous vendor entry can be easily edited or deleted later. No financial transactions, code execution, or irreversible actions are involved.

From the tool's definition Tool description states 'Add a new vendor to the Vendors sheet' — the verb 'Add' indicates creation/insertion of data into a structured sheet without deletion or execution of external operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_vendor Rate-limited

add_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": {
    "add_vendor": {
      "limits": [
        {
          "counter": "add_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 add_vendor

What does the add_vendor tool do? +

Add a new vendor to the Vendors sheet. 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 add_vendor? +

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

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

Can I rate-limit add_vendor? +

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

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

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