payware_products_update_schedule · Payware MCP Server MCP

WHAT IT DOES

What payware_products_update_schedule does on Payware MCP Server

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

WHY IT NEEDS A POLICY

Why payware_products_update_schedule needs a policy

The tool creates or modifies data (price schedule) reversibly, fitting the Write category. Severity is high because unauthorized price schedule updates could directly impact transaction pricing, revenue calculations, and customer billing—critical to payment processing systems.

From the tool's definition Tool name contains 'update' and description states 'Update an existing price schedule'; this modifies existing data in a reversible manner (price schedules can be updated again or reverted). ISV operation indicates merchant-level configuration authority.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

payware_products_update_schedule Rate-limited

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

FAQ

Questions about payware_products_update_schedule

What does the payware_products_update_schedule tool do? +

Update an existing price schedule (ISV operation). It is categorised as a Write tool in the Payware 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 payware_products_update_schedule? +

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

What risk level is payware_products_update_schedule? +

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

Can I rate-limit payware_products_update_schedule? +

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

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

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