Get the purchase history from a user's Kroger account via API.
AI agents call get_purchases to retrieve information from Get Gather without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves purchase history data from a Kroger account without modifying, deleting, or executing operations. It falls clearly into the Read category. Severity is high because purchase history is sensitive personal data that reveals shopping patterns, dietary preferences, financial behavior, and personal habits — misuse by an AI agent could lead to privacy violations and unauthorized data exposure, even…
From the tool's definition Tool name is 'get_purchases' and description states 'Get the purchase history from a user's Kroger account via API' — the verb 'Get' and action of retrieving purchase history indicate data retrieval with no modification or deletion.
Documented attack patterns abuse exactly the kind of access get_purchases gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Get Gather, and nothing reaches the server without passing your rules. This is the rule we recommend for get_purchases:
{
"version": "1",
"default": "deny",
"tools": {
"get_purchases": {}
}
}get_purchases is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the purchase history from a user's Kroger account via API. It is categorised as a Read tool in the Get Gather MCP Server, which means it retrieves data without modifying state.
Register the Get Gather MCP server in PolicyLayer and add a rule for get_purchases: 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 Get Gather. Nothing to install.
get_purchases 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_purchases 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_purchases. 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_purchases is provided by the Get Gather MCP server (remotebrowser/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 62 Get Gather tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
62 Get Gather tools catalogued and risk-classified — across an index of 42,500+ MCP servers.