trust-attest-temporal
Create and publish an attestation with occurredAt field — records when the attested event actually happened, which may differ from the publication time. Also supports validFrom/validTo for deferred activation and validity windows.
This record as markdown: /tools/dev-forgesworn-bray/trust-attest-temporal.md
What trust-attest-temporal does on Nostr Bray
AI agents use trust-attest-temporal to create or update resources in Nostr Bray, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nostr Bray environment.
Why trust-attest-temporal is rated Medium
This tool creates and publishes new attestation records on a Nostr-based trust system. Creating attestations is a reversible write operation (attestations can theoretically be revoked or superseded), not destructive deletion.
From the tool's definition 'Create and publish an attestation' — explicitly performs creation and publication of data (attestation records) with temporal metadata (occurredAt, validFrom, validTo).
Attacks that exploit this kind of access
The rule that runs trust-attest-temporal safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nostr Bray, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For trust-attest-temporal, this is the rule to start with:
trust-attest-temporal stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nostr Bray, apply this rule, and every trust-attest-temporal call is checked against it from then on.
Questions about trust-attest-temporal
Create and publish an attestation with occurredAt field — records when the attested event actually happened, which may differ from the publication time. Also supports validFrom/validTo for deferred activation and validity windows. It is categorised as a Write tool in the Nostr Bray MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nostr Bray MCP server in PolicyLayer and add a rule for trust-attest-temporal: 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 Nostr Bray. Nothing to install.
trust-attest-temporal is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the trust-attest-temporal 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 trust-attest-temporal. 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.
trust-attest-temporal is provided by the Nostr Bray MCP server (nostr-bray). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nostr Bray, and thousands of servers like it.
This server
Across the catalogue