FraudLabs Pro MCP integration for AI agents.
Connect AI agents to FraudLabs Pro through 3 structured actions, including get order result, feedback order, and screen order. Review authentication, inputs…
- ACTION CONTRACTS
- 3
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the FraudLabs Pro integration exposes
The FraudLabs Pro Agent App exposes 3 provider-backed actions for security and data work. Its current contract lets an authorized agent retrieve a fraudlabs pro order screening result by transaction id, send approve or reject feedback for a fraudlabs pro order transaction, and screen an order transaction for fraud risk with fraudlabs pro. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected FraudLabs Pro account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real FraudLabs Pro capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_order_resultREADRetrieve a FraudLabs Pro order screening result by transaction id.
INPUTS: id
feedback_orderREVIEWSend approve or reject feedback for a FraudLabs Pro order transaction.
INPUTS: id / action / note
screen_orderREVIEWScreen an order transaction for fraud risk with FraudLabs Pro.
INPUTS: ip / userOrderId / email / amount / currency
INPUT CONTRACTS
Know what the action needs before it runs.
get_order_result
idREQUIRED- The FraudLabs Pro transaction id returned by the Screen Order API.
feedback_order
idREQUIRED- The FraudLabs Pro transaction id returned by the Screen Order API.
actionREQUIRED- The feedback action to apply to the transaction.
noteOPTIONAL- Optional merchant note explaining the feedback decision.
screen_order
ipREQUIRED- The customer IP address for the transaction.
userOrderIdOPTIONAL- The merchant order id for the transaction.
emailOPTIONAL- The customer email address.
amountOPTIONAL- The transaction amount.
currencyOPTIONAL- The ISO 4217 currency code for the transaction.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Order Result
Retrieve a FraudLabs Pro order screening result by transaction id. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_order_resultVerify with Feedback Order
Send approve or reject feedback for a FraudLabs Pro order transaction. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
feedback_orderSAFETY BOUNDARY
Operate FraudLabs Pro with explicit limits
- Authorize FraudLabs Pro with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned FraudLabs Pro data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in FraudLabs Pro rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the FraudLabs Pro task completed successfully.
CONNECTION MODEL
API key
FraudLabs Pro API license key passed as the key parameter. Get it from your FraudLabs Pro merchant area: https://www.fraudlabspro.com/merchant/sign-in.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 1
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by FraudLabs Pro.