update_brand · Peecai MCP: Risk & Policy

WHAT IT DOES

What update_brand does on Peecai

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

WHY IT NEEDS A POLICY

Why update_brand needs a policy

This tool modifies existing data (brand attributes) reversibly. While the metric recalculation side effect adds complexity, the core action is an update/write operation. It does not delete data irreversibly (ruling out Destructive), does not execute arbitrary code (ruling out Execute), and does not involve financial transactions.

From the tool's definition Tool description states 'Update an existing brand', which is a modification operation. 'Changing name, aliases, or regex triggers metric recalculation' indicates side effects but not destructive deletion—the operation is reversible.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_brand Rate-limited

update_brand 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_brand": {
      "limits": [
        {
          "counter": "update_brand_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 Peecai, so you can run agents against it safely.

FAQ

Questions about update_brand

What does the update_brand tool do? +

Update an existing brand. Changing name, aliases, or regex triggers metric recalculation. It is categorised as a Write tool in the Peecai 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_brand? +

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

What risk level is update_brand? +

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

Can I rate-limit update_brand? +

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

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

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