Compute VDF beats and submit to the Registry to credit this agent's lifetime beat count. Unlike provenonce_beats_proof (which gets a receipt for spawn/resync), this extends the agent's persistent beat chain and increases the "Lifetime Beats" metric visible in the Registry.
Part of the Provenonce MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use provenonce_submit_beats to create or modify resources in Provenonce. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call provenonce_submit_beats repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Provenonce.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
provenonce_submit_beats:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Provenonce policy for all 11 tools.
Agents calling write-class tools like provenonce_submit_beats have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Compute VDF beats and submit to the Registry to credit this agent's lifetime beat count. Unlike provenonce_beats_proof (which gets a receipt for spawn/resync), this extends the agent's persistent beat chain and increases the "Lifetime Beats" metric visible in the Registry.. It is categorised as a Write tool in the Provenonce MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for provenonce_submit_beats. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Provenonce MCP server.
provenonce_submit_beats 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 provenonce_submit_beats rule in your Intercept 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 Intercept policy for provenonce_submit_beats. 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.
provenonce_submit_beats is provided by the Provenonce MCP server (@provenonce/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept