Get information about an OAuth2 access token. This endpoint exposes information about access tokens, including their status. Only information about tokens requested by the ISV is returned. Use this to check token status and present information to users in POS software. Endpoint: GET /oauth2/token...
AI agents call payware_authorization_oauth2_get_token_info 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 is a Read operation—it retrieves and queries token information without creating, modifying, or deleting data. Severity is medium rather than low because token information can be sensitive in payment processing contexts and could be used to enumerate valid tokens or understand authentication state.
From the tool's definition Tool performs GET request to retrieve 'information about access tokens, including their status' with no modification or deletion capability. Description explicitly states 'Get information' and 'check token status'.
Attacks that exploit this kind of access
Get information about an OAuth2 access token. This endpoint exposes information about access tokens, including their status. Only information about tokens requested by the ISV is returned. Use this to check token status and present information to users in POS software. Endpoint: GET /oauth2/tokens/{token} Auth: Requires ISV JWT 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_authorization_oauth2_get_token_info: 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_authorization_oauth2_get_token_info 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_authorization_oauth2_get_token_info 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_authorization_oauth2_get_token_info. 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_authorization_oauth2_get_token_info 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 →