Low Risk

verify_proof_of_play

Verify cryptographic proof of ad delivery or get campaign proofs. Requires either campaign_id or proof_payload (at least one must be provided). Two modes: 1. Verify a proof: pass proof_payload with signature fields to verify 2. Get proofs: pass campaign_id to get Ed25519-signed proofs for a campa...

Risk signalsHigh parameter count (13 properties)

Part of the Trillboards DOOH Advertising server.

verify_proof_of_play is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE TRILLBOARDS DOOH ADVERTISING →

Free to start. No card required.

AI agents call verify_proof_of_play to retrieve information from Trillboards DOOH Advertising without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though verify_proof_of_play only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "verify_proof_of_play": {}
  }
}

See the full Trillboards DOOH Advertising policy for all 74 tools.

Get this rule live on your own Trillboards DOOH Advertising server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TRILLBOARDS DOOH ADVERTISING →

View all 74 tools →

These attack patterns abuse exactly the kind of access verify_proof_of_play gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so verify_proof_of_play only ever does what you allow.

SECURE TRILLBOARDS DOOH ADVERTISING →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the verify_proof_of_play tool do? +

Verify cryptographic proof of ad delivery or get campaign proofs. Requires either campaign_id or proof_payload (at least one must be provided). Two modes: 1. Verify a proof: pass proof_payload with signature fields to verify 2. Get proofs: pass campaign_id to get Ed25519-signed proofs for a campaign Uses Ed25519 signatures (v2) that can be independently verified by third parties using the Trillboards public key. WHEN TO USE: - Verifying that ads were actually delivered to screens - Exporting cryptographically signed proof records for auditors - Getting proof-of-play data for campaign transparency reports RETURNS (verify mode): - valid: boolean, reason: string if invalid, version: 'v1' or 'v2' RETURNS (get proofs mode): - campaignId, totalImpressions, proofsReturned - proofs: Array of signed impression proofs - pagination: { limit, hasMore, nextCursor } - signatureVersion, publicKeyUrl EXAMPLE (verify): verify_proof_of_play({ proof_payload: { signature: "ed25519=abc123...", timestamp: "2026-03-10T15:30:00Z", adId: "ad_123", impressionId: "imp_456", screenId: "scr_789", deviceId: "dev_012" } }) EXAMPLE (get proofs): verify_proof_of_play({ campaign_id: "camp_abc123", start_date: "2026-03-01", end_date: "2026-03-10" }). It is categorised as a Read tool in the Trillboards DOOH Advertising MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on verify_proof_of_play? +

Register the Trillboards DOOH Advertising MCP server in PolicyLayer and add a rule for verify_proof_of_play: 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 Trillboards DOOH Advertising. Nothing to install.

What risk level is verify_proof_of_play? +

verify_proof_of_play is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit verify_proof_of_play? +

Yes. Add a rate_limit block to the verify_proof_of_play 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.

How do I block verify_proof_of_play completely? +

Set action: deny in the PolicyLayer policy for verify_proof_of_play. 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.

What MCP server provides verify_proof_of_play? +

verify_proof_of_play is provided by the Trillboards DOOH Advertising MCP server (https://api.trillboards.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Trillboards DOOH Advertising tool call.

Deterministic rules across all 74 Trillboards DOOH Advertising 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.