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...
High parameter count (12 properties)
Part of the Clevername MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
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. Intercept'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.
tools:
guard_register_agent:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Clevername policy for all 67 tools.
Agents calling write-class tools like guard_register_agent 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.
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.
Add a rule in your Intercept YAML policy under the tools section for guard_register_agent. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Clevername MCP server.
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 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 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). 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