Agent Consent · Checks on the principal's grant before an agent uses data

Covered, current, standing, proven, before the data is used.

An agent is ready to use a principal's data, or act on it, when the grant covers this use by name: the data, the action and the recipient; the grant is still within its term for the whole use, including a use that finishes after the term ends; no withdrawal reaches the use, and every system holding the data has applied the ones made; a complete record shows who granted, when, how they agreed and what they were shown; the use serves the purpose the grant was given for; the data passes on only as the grant allows; fresh consent is in hand wherever the grant or a change since it calls for it; and the consent ledger entry matches its events. Agent Consent checks each of those with eight tools: eight checks. These checks read the grant the principal gave over their own data; the agent's authority to act is a separate check. Your agent sends the grant and the planned use, the term, the withdrawal log with the systems that hold the data, the consent record, the purposes, the onward rule with a planned transfer, the confirmations and changes or the ledger entry with its events in the call, and each tool returns a signed report that names what is out of scope, expired, revoked, missing, mismatched, barred, overdue or misrecorded, with the fix for each.

See the tools Read the contract

Tool access: 0.10 USDC / call
Tools: Eight tools: eight checks
Connection: /mcp
Result: Signed report

The eight tools.

Each tool reads one question about a principal's grant and answers it from the record. Every tool reads the recorded material in the call: grants, planned uses, withdrawals, consent records, purposes, transfers, confirmations and ledger entries go in, and a classification comes out. The report names the item, date, withdrawal, system, purpose, condition or event behind every finding, with the fix for each gap, so your agents and you see why it reads the way it does.

`wever_consent-scope-check`

Reads: The principal’s grant with the data, actions and recipients it covers and rules out by name, who it was given to and its wording, beside the planned use with who runs it, the data it touches, the action it takes and its recipients.
The signed report states: Data, an action or a recipient outside the grant, anything the grant rules out by name and a use run by another party than the grantee, then items covered only by catch-all wording such as any data or our partners.
Price: 0.10 USDC per call
Verdicts: consent_out_of_scopeconsent_scope_partialconsent_scope_unclearconsent_in_scope

`wever_consent-expiry-check`

Reads: When the grant was given, its end date or its term, whether it runs until withdrawn and its wording, beside when the use starts and ends or whether it is ongoing.
The signed report states: A grant that ended before the use, a use that finishes after the grant ends, an ongoing use against a grant that ends, an end inside the warning window, and a term that is open-ended or names no length.
Price: 0.10 USDC per call
Verdicts: consent_expiredconsent_expiringconsent_expiry_unknownconsent_current

`wever_consent-revocation-check`

Reads: Every withdrawal the principal made, whole or in part, with when it was made and what it withdraws, when the log was read, and each system that holds the data with whether and when it applied the withdrawal.
The signed report states: A withdrawal that reaches the use, a system that never applied it, a partial withdrawal the use stays outside, and systems still applying it, unknown or slower than the target.
Price: 0.10 USDC per call
Verdicts: consent_revokedconsent_revocation_partialconsent_revocation_uncheckedconsent_standing

`wever_consent-evidence-check`

Reads: The consent record: who granted and how their identity is known, when, how it was captured, the notice and version the principal saw and when, where the record is kept and who captured it.
The signed report states: No grantor, time or method, capture by a pre-ticked box, a default left on, a line in the terms or inference, wording that assumes consent, a notice shown after the consent, and gaps in the notice, version and capture.
Price: 0.10 USDC per call
Verdicts: consent_evidence_missingconsent_evidence_partialconsent_evidence_unverifiableconsent_evidenced

`wever_consent-purpose-check`

Reads: The purposes the grant was given for and the ones it rules out, its wording, and the use’s main purpose, its other purposes and its own wording.
The signed report states: A purpose the grant does not name or rules out, a purpose the use’s own wording serves without declaring it, such as training a model or advertising, and a purpose covered only by wording such as related purposes.
Price: 0.10 USDC per call
Verdicts: consent_purpose_mismatchconsent_purpose_stretchedconsent_purpose_unclearconsent_purpose_aligned

`wever_consent-transfer-check`

Reads: What the grant says about passing the data on and to sub-agents, the recipients it names and its wording, beside the planned transfer with its recipient, data and the conditions on the recipient.
The signed report states: A transfer the grant bars, a recipient it does not name, fresh consent it requires and nobody asked for, a recipient free to pass the data on, and conditions still to meet before the transfer.
Price: 0.10 USDC per call
Verdicts: consent_transfer_barredconsent_transfer_conditionalconsent_transfer_unspecifiedconsent_transferable

`wever_consent-renewal-check`

Reads: When the grant was given and last confirmed, how often it must be confirmed, how it renews and when confirmation was last asked for, with every change since the grant and when the principal agreed to it.
The signed report states: A confirmation date already passed, a change the principal never agreed to, a grant that renews by itself, a due date inside the warning window and a request still unanswered.
Price: 0.10 USDC per call
Verdicts: consent_renewal_overdueconsent_renewal_pendingconsent_renewal_terms_unknownconsent_renewal_current

`wever_consent-record-check`

Reads: The consent ledger entry with its principal, grantee, scope, purposes, dates, capture method, notice version and status, and the events behind it: granted, narrowed, widened, renewed, revoked, expired and used.
The signed report states: An entry with no record of who granted, to whom or when, a status that misses a withdrawal, an expiry or a narrowing, uses outside the grant’s life, data beyond what was granted, and missing parts.
Price: 0.10 USDC per call
Verdicts: consent_record_missingconsent_record_incompleteconsent_record_unverifiableconsent_record_complete

Start with the two free tools.

On https://weverlabs.com/mcp-free, anonymous and with no wallet, two Agent Consent tools show what a sound consent record holds and what a well-kept consent looks like beside a flawed one. Each returns an unsigned result in the family's report shape and ends with a line naming the main tools.

`wever_consent-snapshot`

Reads: A consent name, a kind of data use such as health data, marketing messages or model training, and optionally the names of the materials in hand.
Returns: The orientation checklist of a sound consent record for that kind of data use, part by part from what the grant covers to the ledger entry it leaves behind, with the items the kind of use adds, the check that reads each part and the materials named beside it.
Access: Free on /mcp-free

`wever_consent-record-sample`

Reads: Nothing, or one sample data use: clinic appointment reminders, a research survey or support chat transcripts.
Returns: One worked consent record kept right beside a flawed one that reaches data the grant rules out, runs past the grant’s end, ignores a withdrawal, rests on a pre-ticked box, hides a purpose, hands the data to a third party and lets its confirmation lapse, each piece annotated with why it passes or fails, scored by seven of the family checks. The checks read your own consent records.
Access: Free on /mcp-free

How agents and people use it.

Your agents

Pull the checklist with wever_consent-snapshot when a new kind of data use is planned, so scope, term, withdrawals, evidence, purpose, onward transfer, renewal and the ledger are on the record before the data is touched.
Call the check that answers the question on https://weverlabs.com/mcp at the moment it matters: before a use starts, before it runs past a date, after reading the withdrawal log, when the consent record is first relied on, when a use gains a purpose, before data passes to a third party or a sub-agent, before a use continues past a confirmation date or a change, and whenever the ledger entry is written.
Act on the verdict and keep the signed report beside the consent record, so every use of the data carries the check behind it.

You

See exactly which data, action and recipient each use relies on, and which of them the grant covers by name.
Spot a withdrawal that a system never applied, or a purpose the principal never agreed to, before the data is used.
Read a consent ledger whose status matches its events, and verify any check against Wever's published trust key whenever you need to show where a verdict came from.

A worked example

One grant, and the use that reaches past it.

The request

{
  "name": "wever_consent-scope-check",
  "arguments": {
    "grant": {
      "id": "G-104",
      "principal": "the patient",
      "grantee": "the reminder agent",
      "data": [
        "phone number",
        "appointment times"
      ],
      "actions": [
        "send reminders"
      ],
      "recipients": [
        "the patient"
      ],
      "excluded": [
        "diagnosis notes"
      ],
      "text": "Text me a reminder the day before each appointment."
    },
    "use": {
      "actor": "the reminder agent",
      "data": [
        "phone number",
        "appointment times",
        "diagnosis notes"
      ],
      "action": "send reminders",
      "recipients": [
        "the patient",
        "a pharmacy partner"
      ]
    }
  }
}

What the report returns

Verdict: consent_out_of_scope.

Finding, recipient outside grant	1 recipient the use relies on is not in the grant: “a pharmacy partner”; the grant names “the patient”.
Finding, excluded by grant	The grant rules out “diagnosis notes” by name, and the use reaches it.
Fix, recipient outside grant	Send the data or the result only to recipients the grant names, or ask the principal to add this one first.
Fix, excluded by grant	Drop what the grant rules out by name; the principal excluded it, so no other wording in the grant covers it.

The use reaches past the grant: recipient outside grant and excluded by grant.

The patient granted the reminder agent their phone number and appointment times to send reminders back to them, and ruled out their diagnosis notes by name. The planned use keeps the phone number, the appointment times, the action and the patient as recipient, so those items are covered. It also reaches the diagnosis notes the patient excluded and sends to a pharmacy partner the grant never names. Taking the diagnosis notes out of the use and keeping the patient as the only recipient, or asking the patient to grant both first, brings the read to consent_in_scope.

Call it from your agent.

Connect to https://weverlabs.com/mcp and call any of the eight tools. Each call costs 0.10 USDC on Base. Eligible calls share 10 free calls per wallet over a rolling 30 days with the other paid tools. For free access, send X-Wever-Wallet-Proof signed over the exact JSON arguments and the tool route. The payment challenge supplies the x402 terms for a paid call.

Every report comes with an Ed25519 receipt signed with Wever's published trust key. The Agent Consent contract lists the schemas, limits, verdicts and signing details. For the agent's own authority to act, Agent Readiness; for trading and treasury mandates, Trading mandates; for the bounds of a delegation, Agent Delegation; for one sharing event against the owner's sharing rules, Agent Operations; for whether a principal agreed to be remembered, Agent Memory; for a data sample's fields, Data evidence check; for purchases against their governing terms, Agent Governance; for promises the agent makes, Agent Commitments; for the objective the work serves, Agent Goals.

Browse all tools