Get all price schedules for a merchant
AI agents call payware_products_get_schedules to retrieve information from Payware MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves price schedule information for a merchant without modifying, deleting, or executing any operations. It is a straightforward data retrieval operation. While the server context involves payment processing, this specific tool does not move money, create transactions, or perform any financial operations—it only reads configuration data.
From the tool's definition Tool name 'get_schedules' and description 'Get all price schedules for a merchant' indicate a retrieval operation with no side effects. The verb 'get' combined with 'all price schedules' clearly denotes a read-only query of existing data.
Attacks that exploit this kind of access
Get all price schedules for a merchant. It is categorised as a Read tool in the Payware MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Payware MCP Server MCP server in PolicyLayer and add a rule for payware_products_get_schedules: 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.
payware_products_get_schedules is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the payware_products_get_schedules 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.
Set action: deny in the PolicyLayer policy for payware_products_get_schedules. 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.
payware_products_get_schedules 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →