List purchase IDs for a specific advertiser.
AI agents call vibe.purchases.list to retrieve information from Vibe Co 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 purchase data for an advertiser without creating, modifying, or deleting any information. It is a standard read operation. Severity is medium rather than low because purchase data can be sensitive business information (financial transaction records), and unauthorized access could expose advertiser spending patterns and transaction history, though the tool itself does not execute code or modify…
From the tool's definition Tool name contains 'list' and description states 'List purchase IDs for a specific advertiser' — a retrieval operation with no modification or deletion.
Attacks that exploit this kind of access
List purchase IDs for a specific advertiser. It is categorised as a Read tool in the Vibe Co MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vibe Co MCP Server MCP server in PolicyLayer and add a rule for vibe.purchases.list: 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 Vibe Co MCP Server. Nothing to install.
vibe.purchases.list 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 vibe.purchases.list 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 vibe.purchases.list. 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.
vibe.purchases.list is provided by the Vibe Co MCP Server MCP server (jacob-hartmann/vibeco-mcp). 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 →