Create a tamper-proof cryptographic record of an agent decision. Signs the event with Ed25519, links it to the previous event in a hash chain (AISS v2.0). Call this after every significant agent action. Required for GDPR Art.22, EU AI Act Art.13, HIPAA audit trail, SEC/FINRA trading compliance.
Risk signalsAccepts raw HTML/template content (payload) · Bulk/mass operation — affects multiple targets
Part of the Piqrypt server.
Free to start. No card required.
AI agents use piqrypt_stamp_event to create or modify resources in Piqrypt. 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 piqrypt_stamp_event repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Piqrypt.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"piqrypt_stamp_event": {
"limits": [
{
"counter": "piqrypt_stamp_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Piqrypt policy for all 4 tools.
These attack patterns abuse exactly the kind of access piqrypt_stamp_event gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Create a tamper-proof cryptographic record of an agent decision. Signs the event with Ed25519, links it to the previous event in a hash chain (AISS v2.0). Call this after every significant agent action. Required for GDPR Art.22, EU AI Act Art.13, HIPAA audit trail, SEC/FINRA trading compliance.. It is categorised as a Write tool in the Piqrypt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Piqrypt MCP server in PolicyLayer and add a rule for piqrypt_stamp_event: 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 Piqrypt. Nothing to install.
piqrypt_stamp_event 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 piqrypt_stamp_event 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 piqrypt_stamp_event. 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.
piqrypt_stamp_event is provided by the Piqrypt MCP server (@piqrypt/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Piqrypt 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.