Returns server health information and validates Stripe API connectivity.
AI agents call stripe_status to retrieve information from Stripe Fraud MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a simple health check and connectivity validation tool. It retrieves status information without creating, modifying, or deleting any data. Even though it's on a server with Financial and Destructive capabilities (refunds, raw API access), this specific tool is a read-only diagnostic operation. Low severity due to minimal blast radius—it cannot be abused to cause financial harm or data loss.
From the tool's definition Tool returns server health information and validates API connectivity. The description indicates it 'Returns' data with no modification, creation, or deletion of resources. No side effects beyond querying status.
Attacks that exploit this kind of access
Returns server health information and validates Stripe API connectivity. It is categorised as a Read tool in the Stripe Fraud MCP MCP Server, which means it retrieves data without modifying state.
Register the Stripe Fraud MCP server in PolicyLayer and add a rule for stripe_status: 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 Fraud MCP. Nothing to install.
stripe_status 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 stripe_status 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 stripe_status. 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.
stripe_status is provided by the Stripe Fraud MCP server (keithah/stripe-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 →