Poll status of a Solana payment bridge after a 202 response from flipr_flip. Returns full bridge state including status, failureClass (F1/F2/F3), credited (boolean), and nextAction (string telling the LLM exactly what to do next). Read nextAction first — it tells you whether to retry, poll again,...
Part of the Flipr X402 server.
Free to start. No card required.
AI agents call flipr_bridge_status to retrieve information from Flipr X402 without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though flipr_bridge_status only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"flipr_bridge_status": {}
}
}See the full Flipr X402 policy for all 19 tools.
These attack patterns abuse exactly the kind of access flipr_bridge_status gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Poll status of a Solana payment bridge after a 202 response from flipr_flip. Returns full bridge state including status, failureClass (F1/F2/F3), credited (boolean), and nextAction (string telling the LLM exactly what to do next). Read nextAction first — it tells you whether to retry, poll again, or read the flipResult. Accepts payment on Base mainnet OR Solana mainnet (auto-bridged). See http://localhost:4402/integration#solana for details. [paymentNetworks: ["base","solana"]] FREE — rate-limited only. [pricing: {"cost":"0","currency":"FREE","type":"free","network":"eip155:8453"}]. It is categorised as a Read tool in the Flipr X402 MCP Server, which means it retrieves data without modifying state.
Register the Flipr X402 MCP server in PolicyLayer and add a rule for flipr_bridge_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 Flipr X402. Nothing to install.
flipr_bridge_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 flipr_bridge_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 flipr_bridge_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.
flipr_bridge_status is provided by the Flipr X402 MCP server (https://flipr-x402.fly.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 Flipr X402 tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.