add_venue · Palate MCP: Risk & Policy

WHAT IT DOES

What add_venue does on Palate

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

WHY IT NEEDS A POLICY

Why add_venue needs a policy

This tool creates new venue entries in a network database. While this modifies shared state and could be abused to spam the network with fake venues, the operation is reversible and does not irreversibly delete data, execute arbitrary code, or move funds. Medium severity reflects potential for abuse (flooding network with junk venues) but limited blast radius in a collaborative agent system.

From the tool's definition Tool name 'add_venue' and description 'Add a new venue to the Palate Network' indicate creation of new data records. The action is reversible (venues can presumably be removed or edited), and no destructive operations are mentioned.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_venue Rate-limited

add_venue 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_venue": {
      "limits": [
        {
          "counter": "add_venue_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 Palate, so you can run agents against it safely.

FAQ

Questions about add_venue

What does the add_venue tool do? +

Add a new venue to the Palate Network. Types: Restaurant, Cafe, Bar, Bakery, Food Truck, Fine Dining, Fast Casual, Coffee Shop, Workspace, Lounge. It is categorised as a Write tool in the Palate 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_venue? +

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

What risk level is add_venue? +

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

Can I rate-limit add_venue? +

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

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

add_venue is provided by the Palate MCP server (palate-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.