query_payment_order
AI agents call query_payment_order to retrieve information from Lfwin Payment without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite operating in a financial domain, this tool retrieves payment information without creating, modifying, or moving money. The query prefix and its distinction from sibling tools like 'create_payment_order' and 'refund_payment_order' confirm it is a Read operation.
From the tool's definition Tool name 'query_payment_order' indicates a query/status-check operation on existing payment data. Server description explicitly mentions 'checking payment status' as a capability.
Attacks that exploit this kind of access
query_payment_order. It is categorised as a Read tool in the Lfwin Payment MCP Server, which means it retrieves data without modifying state.
Register the Lfwin Payment MCP server in PolicyLayer and add a rule for query_payment_order: 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 Lfwin Payment. Nothing to install.
query_payment_order 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 query_payment_order 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 query_payment_order. 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.
query_payment_order is provided by the Lfwin Payment MCP server (litsen/lfwin-payment-mcp). 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 →