request_purchaser_info
A read tool on the Pop Pay MCP server.
This record as markdown: /tools/100xpercent-pop-pay-python/request-purchaser-info.md
What request_purchaser_info does on Pop Pay
AI agents call request_purchaser_info to retrieve information from Pop Pay without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why request_purchaser_info is rated Low
The tool appears to retrieve purchaser information without modifying or executing transactions. However, confidence is moderate due to lack of descriptive detail. In a payment guardrail system, retrieving purchaser details is a necessary precondition for financial operations but does not itself move money or trigger irreversible actions, classifying it as Read rather than Financial/Destructive/Execute.
From the tool's definition Tool name 'request_purchaser_info' indicates retrieval of purchaser information. Description is empty, limiting evidence, but the naming convention follows a query/retrieval pattern (request_*) consistent with Read operations.
Attacks that exploit this kind of access
The rule that runs request_purchaser_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pop Pay, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For request_purchaser_info, this is the rule to start with:
request_purchaser_info 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 Pop Pay, apply this rule, and every request_purchaser_info call is checked against it from then on.
Questions about request_purchaser_info
request_purchaser_info is a read tool on the Pop Pay MCP server. It is categorised as a Read tool in the Pop Pay MCP Server, which means it retrieves data without modifying state.
Register the Pop Pay MCP server in PolicyLayer and add a rule for request_purchaser_info: 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 Pop Pay. Nothing to install.
request_purchaser_info 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 request_purchaser_info 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 request_purchaser_info. 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.
request_purchaser_info is provided by the Pop Pay MCP server (100xpercent/pop-pay-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pop Pay, and thousands of servers like it.
This server
Across the catalogue