updateCategory · Omnisend MCP Server MCP: Risk & Policy

WHAT IT DOES

What updateCategory does on Omnisend MCP Server

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

WHY IT NEEDS A POLICY

Why updateCategory needs a policy

This tool modifies existing category data in the Omnisend marketing platform. It is categorized as Write because it creates or modifies data reversibly—the changes can be undone by updating again. Severity is medium because misconfiguration could affect marketing categories and product organization, but the blast radius is limited to category metadata without direct financial or destructive impact.

From the tool's definition Tool name 'updateCategory' and description 'Update an existing product category' indicates modification of existing data. The instruction to 'preserve the returned structure when updating' confirms this is a reversible update operation, not destructive.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

updateCategory Rate-limited

updateCategory 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": {
    "updateCategory": {
      "limits": [
        {
          "counter": "updatecategory_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 Omnisend MCP Server, so you can run agents against it safely.

FAQ

Questions about updateCategory

What does the updateCategory tool do? +

Update an existing product category. IMPORTANT: You must first get the category using getCategory and preserve the returned structure when updating. It is categorised as a Write tool in the Omnisend 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 updateCategory? +

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

What risk level is updateCategory? +

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

Can I rate-limit updateCategory? +

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

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

updateCategory is provided by the Omnisend MCP Server MCP server (plutzilla/omnisend-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.