Register an ATAP v0.1 Agent Identity Token for a media-buying agent. Sigil validates the capabilities + constraints against the sigil:media_buyer:v1 profile, signs the AIT as the witness, and returns it. Do this once per agent campaign before witnessing any events. Inputs: - profile (required): m...
Part of the Sigil server.
Free to start. No card required.
AI agents use sigil_atap_register_ait to create or modify resources in Sigil. 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 sigil_atap_register_ait 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 Sigil.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"sigil_atap_register_ait": {
"limits": [
{
"counter": "sigil_atap_register_ait_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Sigil policy for all 12 tools.
These attack patterns abuse exactly the kind of access sigil_atap_register_ait 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.
Register an ATAP v0.1 Agent Identity Token for a media-buying agent. Sigil validates the capabilities + constraints against the sigil:media_buyer:v1 profile, signs the AIT as the witness, and returns it. Do this once per agent campaign before witnessing any events. Inputs: - profile (required): must be sigil:media_buyer:v1. - operator (required): the agent operator's canonical OAI. - capabilities (required): array from the profile vocabulary. - constraints (required): { currency, max_bid_cpm, supply_trust_minimum, budget_total_cap, allowed_channels, ... }. - attestation_policy (required): { witness_granularity, block_interval_seconds (60-3600), receipt_generation }. - expires_at (required): ISO date-time, <= 365 days out. Returns: the signed AIT (note its id for subsequent witness calls).. It is categorised as a Write tool in the Sigil MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sigil MCP server in PolicyLayer and add a rule for sigil_atap_register_ait: 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 Sigil. Nothing to install.
sigil_atap_register_ait 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 sigil_atap_register_ait 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 sigil_atap_register_ait. 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.
sigil_atap_register_ait is provided by the Sigil MCP server (https://mcp.sigil.tunnelmind.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Sigil 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.