update_catalog_item · FacturaHub MCP Server MCP

WHAT IT DOES

What update_catalog_item does on FacturaHub MCP Server

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

WHY IT NEEDS A POLICY

Why update_catalog_item needs a policy

This tool modifies existing catalog data but does not irreversibly delete it, execute external code/commands, or handle financial transactions. Changes to item metadata (name, price, description, category) and stock settings are reversible through subsequent updates.

From the tool's definition Tool description states 'Update an existing catalog item — change name, price, description, category, stock settings, etc.' The verb 'update' and the enumeration of modifiable fields (name, price, description, category, stock settings) confirm this creates or…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_catalog_item Rate-limited

update_catalog_item 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_catalog_item": {
      "limits": [
        {
          "counter": "update_catalog_item_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 FacturaHub MCP Server, so you can run agents against it safely.

FAQ

Questions about update_catalog_item

What does the update_catalog_item tool do? +

[FacturaHub] Update an existing catalog item — change name, price, description, category, stock settings, etc. It is categorised as a Write tool in the FacturaHub 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_catalog_item? +

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

What risk level is update_catalog_item? +

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

Can I rate-limit update_catalog_item? +

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

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

update_catalog_item is provided by the FacturaHub MCP Server MCP server (santy1422/facturahub-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.