Query documents in a user collection. Returns up to 50 by default, 1000 max.
AI agents call find to retrieve information from Stripe Reporting without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries data from a user collection with no side effects or state mutations. It is a straightforward read operation returning document results. Severity is low because misuse would only expose financial/operational data already intended to be queryable, not enable destructive or financial actions. Confidence is high due to explicit 'read-only' designation and clear query semantics.
From the tool's definition Tool description states 'Query documents in a user collection. Returns up to 50 by default, 1000 max.' The verb 'Query' and result-returning behavior indicate data retrieval only.
Attacks that exploit this kind of access
Query documents in a user collection. Returns up to 50 by default, 1000 max. It is categorised as a Read tool in the Stripe Reporting MCP Server, which means it retrieves data without modifying state.
Register the Stripe Reporting MCP server in PolicyLayer and add a rule for find: 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 Stripe Reporting. Nothing to install.
find 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 find 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 find. 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.
find is provided by the Stripe Reporting MCP server (ohrytskov/stripe-reporting-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 →