Retrieve customer information by ID
AI agents call retrieve_customer 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 performs a simple data retrieval operation, retrieving customer details by identifier. It has no destructive, financial, or executable characteristics—it merely queries and returns customer information. While customer data is sensitive, the read-only nature and limited blast radius from a misused query operation classifies this as a low-severity Read action.
From the tool's definition Tool name 'retrieve_customer' and description 'Retrieve customer information by ID' indicate a query operation that retrieves existing data without modification or side effects.
Attacks that exploit this kind of access
Retrieve customer information by ID. 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 retrieve_customer: 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.
retrieve_customer 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 retrieve_customer 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 retrieve_customer. 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.
retrieve_customer 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 →