Get transaction history as an ISV on behalf of a merchant. Retrieves both active and completed transactions with optional filtering. Requires ISV authentication with merchant partner ID and OAuth2 token.
AI agents call payware_operations_get_transaction_history 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 historical transaction data without creating, modifying, or deleting records. While it accesses potentially sensitive financial transaction information (warranting medium severity due to data sensitivity and ISV access scope), the action itself is a read-only query.
From the tool's definition Tool description states 'Get transaction history' and 'Retrieves both active and completed transactions' - these are query operations with no modification or deletion of data.
Attacks that exploit this kind of access
Get transaction history as an ISV on behalf of a merchant. Retrieves both active and completed transactions with optional filtering. Requires ISV authentication with 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_operations_get_transaction_history: 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_operations_get_transaction_history 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_operations_get_transaction_history 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_operations_get_transaction_history. 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_operations_get_transaction_history 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 →