List all POIs (Points of Interaction) for a merchant. ISV Authentication: Uses ISV JWT with merchant partner ID and OAuth2 token. Endpoint: GET /poi Use Case: Retrieve all physical payment points configured for a merchant. POI states: IDLE (ready), READY (price set), BUSY (payment in progress), D...
AI agents call payware_poi_list 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 queries and retrieves merchant payment point configuration data without side effects. While it requires authentication (ISV JWT and OAuth2), the operation itself is read-only. The low severity reflects that unauthorized access to POI configuration is a data disclosure risk but not a direct financial threat or destructive action.
From the tool's definition Tool performs a GET request to list POIs with no modification, creation, or deletion capability. Description states 'List all POIs' and 'Retrieve all physical payment points' — purely informational retrieval.
Attacks that exploit this kind of access
List all POIs (Points of Interaction) for a merchant. ISV Authentication: Uses ISV JWT with merchant partner ID and OAuth2 token. Endpoint: GET /poi Use Case: Retrieve all physical payment points configured for a merchant. POI states: IDLE (ready), READY (price set), BUSY (payment in progress), DISABLED. Required: Merchant Partner ID and OAuth2 token for ISV authentication. 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_poi_list: 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_list 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_poi_list 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_list. 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_list 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 →