Save a document to a Mongo collection. Creates the collection on first write. Use for flagged entities, notes, pinned reports, saved cohorts. Passive storage only — nothing monitors saved entities automatically.
AI agents use save to create or update resources in Stripe Reporting — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stripe Reporting environment.
The tool creates or modifies data in MongoDB collections persistently (e.g., flagged entities, notes, pinned reports, saved cohorts). Although the server is advertised as 'read-only' for Stripe reporting, this tool breaks that contract by enabling write operations to backend storage.
From the tool's definition Tool description explicitly states 'Save a document to a Mongo collection' and 'Creates the collection on first write', indicating persistent data creation and modification.
Attacks that exploit this kind of access
Save a document to a Mongo collection. Creates the collection on first write. Use for flagged entities, notes, pinned reports, saved cohorts. Passive storage only — nothing monitors saved entities automatically. It is categorised as a Write tool in the Stripe Reporting MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Stripe Reporting MCP server in PolicyLayer and add a rule for save: 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.
save is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save 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 save. 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.
save 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 →