Create an AP2 payment mandate: a pre-authorization that lets your agent place orders autonomously (human-not-present) within strict limits — total budget, optional per-order cap, currency, optional seller/category scope, and expiry. Returns a mandate_id to pass to place_order. Each order authoriz...
Part of the Buyer Intelligence server.
Free to start. No card required.
AI agents use create_payment_mandate to initiate financial transactions through Buyer Intelligence. Financial operations involve real money and are irreversible once processed. PolicyLayer blocks financial tools by default, requiring explicit human approval with transaction-level limits to prevent unauthorised spending.
create_payment_mandate moves real money. Without a policy, an autonomous agent could initiate transactions that drain accounts or exceed budgets. PolicyLayer blocks financial tools by default, requiring human-in-the-loop approval with configurable spending limits per transaction and per time window.
Financial tools involve real money. Block by default and require explicit human approval before enabling.
{
"version": "1",
"default": "deny",
"tools": {
"create_payment_mandate": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}See the full Buyer Intelligence policy for all 12 tools.
These attack patterns abuse exactly the kind of access create_payment_mandate gives an agent. Each links to the full case and the policy that stops it:
Other financial tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Create an AP2 payment mandate: a pre-authorization that lets your agent place orders autonomously (human-not-present) within strict limits — total budget, optional per-order cap, currency, optional seller/category scope, and expiry. Returns a mandate_id to pass to place_order. Each order authorized against it is recorded as a verifiable intent and decrements the budget. Requires authentication.. It is categorised as a Financial tool in the Buyer Intelligence MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Buyer Intelligence MCP server in PolicyLayer and add a rule for create_payment_mandate: 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 Buyer Intelligence. Nothing to install.
create_payment_mandate 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 create_payment_mandate 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 create_payment_mandate. 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.
create_payment_mandate is provided by the Buyer Intelligence MCP server (https://www.procureradar.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Buyer Intelligence 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.