Get current status of a POI including any pending payment. ISV Authentication: Uses ISV JWT with merchant partner ID and OAuth2 token. Endpoint: GET /poi/{poiId}/status Use Case: Check if a POI is idle, has a pending price, or is busy with a payment. POI States: - IDLE: Ready for new payment - RE...
AI agents call payware_poi_get_status 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 the current operational status of a Point of Integration (POI) device and any associated pending payment information. It performs a read-only query via GET endpoint with no capability to create, modify, delete, or execute transactions. While it accesses payment-system information (requiring OAuth2 authentication), the tool itself does not move funds, execute commands, or alter data.
From the tool's definition Tool description states 'Get current status of a POI including any pending payment' with endpoint 'GET /poi/{poiId}/status'. The GET method and status-checking nature indicate read-only data retrieval with no side effects.
Attacks that exploit this kind of access
Get current status of a POI including any pending payment. ISV Authentication: Uses ISV JWT with merchant partner ID and OAuth2 token. Endpoint: GET /poi/{poiId}/status Use Case: Check if a POI is idle, has a pending price, or is busy with a payment. POI States: - IDLE: Ready for new payment - READY: Price set, waiting for customer scan - BUSY: Payment in progress - DISABLED: Not accepting payments Required: POI ID, Merchant Partner ID, and OAuth2 token. 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_get_status: 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_get_status 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_get_status 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_get_status. 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_get_status 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 →