stateset_get_payments_by_order
Retrieves all payments associated with an order. Use to review payment history, check payment status, or reconcile transactions.
This record as markdown: /tools/stateset-mcp-server/stateset-get-payments-by-order.md
What stateset_get_payments_by_order does on Stateset
AI agents call stateset_get_payments_by_order to retrieve information from Stateset without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why stateset_get_payments_by_order is rated Low
This tool only retrieves and queries existing payment data associated with an order. It performs no writes, deletions, executions, or financial transactions. The verb 'retrieves' and the purely informational use cases (review, check, reconcile) confirm this is a Read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name contains 'get_payments' and description states 'Retrieves all payments' with use cases limited to 'review payment history, check payment status, or reconcile transactions' — all read-only query operations with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs stateset_get_payments_by_order safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stateset, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stateset_get_payments_by_order, this is the rule to start with:
stateset_get_payments_by_order is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Stateset, apply this rule, and every stateset_get_payments_by_order call is checked against it from then on.
Questions about stateset_get_payments_by_order
Retrieves all payments associated with an order. Use to review payment history, check payment status, or reconcile transactions. It is categorised as a Read tool in the Stateset MCP Server, which means it retrieves data without modifying state.
Register the Stateset MCP server in PolicyLayer and add a rule for stateset_get_payments_by_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 Stateset. Nothing to install.
stateset_get_payments_by_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 stateset_get_payments_by_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 stateset_get_payments_by_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.
stateset_get_payments_by_order is provided by the Stateset MCP server (stateset/stateset-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stateset, and thousands of servers like it.
This server
Across the catalogue