Check whether a project has a connected Stripe account
AI agents call get_stripe_status to retrieve information from Prowpt MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves information about whether Stripe is connected to a project. It performs no mutations, executes no code, triggers no payments, and has no destructive effects. It is a simple status check with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_stripe_status' and description 'Check whether a project has a connected Stripe account' indicate a read-only query operation that retrieves configuration status without modifying or executing any financial transactions.
Attacks that exploit this kind of access
Check whether a project has a connected Stripe account. It is categorised as a Read tool in the Prowpt MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Prowpt MCP Server MCP server in PolicyLayer and add a rule for get_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 Prowpt MCP Server. Nothing to install.
get_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 get_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 get_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.
get_stripe_status is provided by the Prowpt MCP Server MCP server (prowptai/prowpt-mcp-server). 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 →