Verify recipient information and bank account
AI agents call verify_recipient 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.
The tool appears to verify/validate recipient information, which is primarily a read/query operation to check if recipient data is valid. However, in some payment systems 'verify' can trigger an external bank verification process (micro-deposits, etc.) which would be Execute. The description is minimal and does not clarify whether this triggers external side effects.
From the tool's definition Verify recipient information and bank account
Attacks that exploit this kind of access
Verify recipient information and bank account. 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 verify_recipient: 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.
verify_recipient 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 verify_recipient 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 verify_recipient. 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.
verify_recipient 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 →