Get details of a specific POI (Point of Interaction). ISV Authentication: Uses ISV JWT with merchant partner ID and OAuth2 token. Endpoint: GET /poi/{poiId} Use Case: Retrieve full details of a physical payment point including configuration and current state. Required: POI ID, Merchant Partner ID...
AI agents call payware_poi_get 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 configuration and state information about a payment point without modifying, creating, or deleting any data. The blast radius of misuse is limited to information disclosure about payment infrastructure, which constitutes a low-severity Read operation. While the information retrieved could be sensitive, the tool itself performs no side effects or irreversible actions.
From the tool's definition Tool performs GET request to retrieve details of a specific POI (Point of Interaction). Description explicitly states 'Retrieve full details' with no modification, creation, or deletion of data. HTTP method is GET, which is read-only.
Attacks that exploit this kind of access
Get details of a specific POI (Point of Interaction). ISV Authentication: Uses ISV JWT with merchant partner ID and OAuth2 token. Endpoint: GET /poi/{poiId} Use Case: Retrieve full details of a physical payment point including configuration and current state. 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: 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 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 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. 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 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 →