List all transfers with optional filtering
AI agents call list_transfers to retrieve information from Omise 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 transfer records from Omise with optional filters. It performs a query operation typical of Read category tools. While it accesses financial transaction data, the tool itself does not move money, create obligations, or modify state—it only retrieves information. The severity is low because misuse would result in unauthorized information disclosure rather than financial loss or destructive action.
From the tool's definition Tool name 'list_transfers' and description 'List all transfers with optional filtering' indicate a retrieval operation with no side effects. The verb 'list' is a standard Read operation that queries existing data without modification.
Attacks that exploit this kind of access
List all transfers with optional filtering. It is categorised as a Read tool in the Omise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Omise MCP Server MCP server in PolicyLayer and add a rule for list_transfers: 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 Omise MCP Server. Nothing to install.
list_transfers 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 list_transfers 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 list_transfers. 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.
list_transfers is provided by the Omise MCP Server MCP server (jun-omise/omise-mcp-alpha). 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 →