Report a confirmed chargeback / fraud outcome back to Legiti. This is Legiti
AI agents use mark_order_fraudulent to commit financial operations through Mcp Ap2 — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool reports fraud/chargeback outcomes to a financial fraud-prevention system (Legiti), which can trigger irreversible financial consequences such as order cancellations, account flags, and chargeback processing. It sits squarely in the Financial category given the payment protocol context (AP2) and direct impact on financial transaction outcomes.
From the tool's definition 'mark_order_fraudulent' — 'Report a confirmed chargeback / fraud outcome back to Legiti'
Documented attack patterns abuse exactly the kind of access mark_order_fraudulent gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for mark_order_fraudulent:
{
"version": "1",
"default": "deny",
"tools": {
"mark_order_fraudulent": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to mark_order_fraudulent is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Report a confirmed chargeback / fraud outcome back to Legiti. This is Legiti. It is categorised as a Financial tool in the Mcp Ap2 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for mark_order_fraudulent: 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 Mcp Ap2. Nothing to install.
mark_order_fraudulent is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the mark_order_fraudulent 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 mark_order_fraudulent. 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.
mark_order_fraudulent is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.