Get a single customer by ID. Returns full customer details including total spent and transaction count.
AI agents call get_customer to retrieve information from Payoza 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 and queries customer data without modifying, deleting, or executing any operations. The verb 'Get' and the output-only nature (returns data) clearly indicate a Read operation. Severity is low because reading customer details poses minimal risk unless sensitive PII is exposed, but the tool itself performs no destructive or financial actions.
From the tool's definition Tool name is 'get_customer' and description states 'Get a single customer by ID. Returns full customer details' — this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get a single customer by ID. Returns full customer details including total spent and transaction count. It is categorised as a Read tool in the Payoza MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Payoza MCP Server MCP server in PolicyLayer and add a rule for get_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 Payoza MCP Server. Nothing to install.
get_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 get_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 get_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.
get_customer is provided by the Payoza MCP Server MCP server (payoza/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_customer is one line of Payoza MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →