Aggregate a batch of Attribution Primitives over a half-open settlement period [t0, t1) into a signed SettlementRecord. Each axis (D, P, G, C) produces a per-contributor total with a balanced-Merkle commitment. Residual buckets pool sub-threshold contributors per Build A §4.1. Output is a fully s...
AI agents use aps_aggregate_settlement to commit financial operations through Agent Passport System — Cryptographic Identity for AI Agents — usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
period | object | Yes | |
receipts | array | Yes | Array of AttributionPrimitives to aggregate |
issued_at | string | — | Override issued_at (canonical ISO-8601 UTC ms + Z); defaults to now |
gateway_did | string | Yes | Gateway DID that signs the record |
gateway_private_key | string | Yes | Ed25519 gateway private key (hex) |
Parameters from the server's own tool schema.
This tool aggregates attribution data into a signed SettlementRecord covering a defined settlement period with per-contributor financial totals. 'Settlement' in financial/attribution contexts implies committing to payment obligations or financial distributions. The signed, Merkle-committed output ready for third-party verification indicates irreversible financial commitments.
From the tool's definition Aggregate a batch of Attribution Primitives over a half-open settlement period [t0, t1) into a signed SettlementRecord... per-contributor total with a balanced-Merkle commitment... Output is a fully signed record ready for third-party verification.
Documented attack patterns abuse exactly the kind of access aps_aggregate_settlement gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent Passport System — Cryptographic Identity for AI Agents, and nothing reaches the server without passing your rules. This is the rule we recommend for aps_aggregate_settlement:
{
"version": "1",
"default": "deny",
"tools": {
"aps_aggregate_settlement": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to aps_aggregate_settlement is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
All 150 Agent Passport System — Cryptographic Identity for AI Agents tools →
Aggregate a batch of Attribution Primitives over a half-open settlement period [t0, t1) into a signed SettlementRecord. Each axis (D, P, G, C) produces a per-contributor total with a balanced-Merkle commitment. Residual buckets pool sub-threshold contributors per Build A §4.1. Output is a fully signed record ready for third-party verification. Spec: BUILD-C-SETTLEMENT-PIPELINE.md. It is categorised as a Financial tool in the Agent Passport System — Cryptographic Identity for AI Agents MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
aps_aggregate_settlement accepts 5 parameters: period, receipts, issued_at, gateway_did, gateway_private_key. Required: period, receipts, gateway_did, gateway_private_key. The full parameter table on this page comes from the server's own tool schema.
Register the Agent Passport System — Cryptographic Identity for AI Agents MCP server in PolicyLayer and add a rule for aps_aggregate_settlement: 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 Agent Passport System — Cryptographic Identity for AI Agents. Nothing to install.
aps_aggregate_settlement 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 aps_aggregate_settlement 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 aps_aggregate_settlement. 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.
aps_aggregate_settlement is provided by the Agent Passport System — Cryptographic Identity for AI Agents MCP server (https://mcp.aeoess.com/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agent Passport System — Cryptographic Identity for AI Agents, 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.
150 Agent Passport System — Cryptographic Identity for AI Agents tools catalogued and risk-classified — across an index of 43,000+ MCP servers.