Subscribes a webhook URL to receive signed POST alerts whenever a watched wallet's persisted attestation is about to expire (attestation.expiring_soon, fires once when within attestation_expiry_warning_days of expires_at) or has expired (attestation.expired, fires once when expires_at crosses). B...
Risk signalsAccepts URL/endpoint input (callback_url)
Part of the InsureLink server.
Free to start. No card required.
AI agents use subscribe_attestation_freshness to create or modify resources in InsureLink. 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 subscribe_attestation_freshness 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 InsureLink.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"subscribe_attestation_freshness": {
"limits": [
{
"counter": "subscribe_attestation_freshness_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full InsureLink policy for all 28 tools.
These attack patterns abuse exactly the kind of access subscribe_attestation_freshness 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.
Subscribes a webhook URL to receive signed POST alerts whenever a watched wallet's persisted attestation is about to expire (attestation.expiring_soon, fires once when within attestation_expiry_warning_days of expires_at) or has expired (attestation.expired, fires once when expires_at crosses). Backed by the same paid drift subscription ($0.01) so the same callback also receives reputation.drift events unless threshold_tier_change=false and threshold_score is set high. 30-day paid window. Each POST includes X-InsureLink-Event header and the schema 'insurelink/attestation-event/v1'. Requires x402 payment ($0.01). Returns payment instructions.. It is categorised as a Write tool in the InsureLink MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the InsureLink MCP server in PolicyLayer and add a rule for subscribe_attestation_freshness: 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 InsureLink. Nothing to install.
subscribe_attestation_freshness 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 subscribe_attestation_freshness 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 subscribe_attestation_freshness. 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.
subscribe_attestation_freshness is provided by the InsureLink MCP server (https://ivnmscuuljqubunqcgkh.supabase.co/functions/v1/mcp-server/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 28 InsureLink 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.