Set a pending price on a POI for customer payment. ISV Authentication: Uses ISV JWT with merchant partner ID and OAuth2 token. Endpoint: PUT /poi/{poiId}/price Use Case: Set the amount a customer should pay when they scan the POI. The POI will transition to READY state and wait for a customer sca...
AI agents use payware_poi_set_price 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.
This tool modifies the state of a Point of Interest (POI) by setting a payment price, causing it to transition to READY state. It creates or modifies data (the pending price) in a reversible way (TTL expires, can be changed), but directly influences the amount a customer will be charged.
From the tool's definition Set a pending price on a POI for customer payment... Set the amount a customer should pay when they scan the POI
Attacks that exploit this kind of access
Set a pending price on a POI for customer payment. ISV Authentication: Uses ISV JWT with merchant partner ID and OAuth2 token. Endpoint: PUT /poi/{poiId}/price Use Case: Set the amount a customer should pay when they scan the POI. The POI will transition to READY state and wait for a customer scan until the TTL expires. Required: POI ID, amount, currency, reason, Merchant Partner ID, and OAuth2 token. 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.
Register the Payware MCP Server MCP server in PolicyLayer and add a rule for payware_poi_set_price: 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_poi_set_price is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the payware_poi_set_price 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_poi_set_price. 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_poi_set_price 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 →