PRE-PROVISIONING / FLEET SETUP ONLY. Register an agent and get a cnk_* token WITHOUT starting an active session. Use for CI/CD pipelines or pre-provisioning before deploy. The token works at POST /v1/guard/chat/completions -- session created lazily on first use (expect +50-200ms on the initial re...
Risk signalsHigh parameter count (12 properties)
Part of the Clevername server.
Free to start. No card required.
AI agents use guard_register_agent to create or modify resources in Clevername. 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 guard_register_agent 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 Clevername.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"guard_register_agent": {
"limits": [
{
"counter": "guard_register_agent_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Clevername policy for all 67 tools.
These attack patterns abuse exactly the kind of access guard_register_agent 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.
PRE-PROVISIONING / FLEET SETUP ONLY. Register an agent and get a cnk_* token WITHOUT starting an active session. Use for CI/CD pipelines or pre-provisioning before deploy. The token works at POST /v1/guard/chat/completions -- session created lazily on first use (expect +50-200ms on the initial request vs. guard_onboard_agent). DECISION: Deploying now? -> guard_onboard_agent (active session + confirmed_settings) Pre-provisioning in CI/CD? -> guard_register_agent (lazy session, +50-200ms first call) Accepts the same parameters as guard_onboard_agent. Returns: agent_id and token (cnk_* -- "cnk_" prefix + 32 alphanumeric chars). ERROR CODES: same as guard_onboard_agent.. It is categorised as a Write tool in the Clevername MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Clevername MCP server in PolicyLayer and add a rule for guard_register_agent: 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 Clevername. Nothing to install.
guard_register_agent 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 guard_register_agent 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 guard_register_agent. 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.
guard_register_agent is provided by the Clevername MCP server (@clevername/clevername-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 67 Clevername 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.