securitypass_register_pack
Save a SecurityPack YAML for the calling tenant. Validates against the schema.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/securitypass-register-pack.md
What securitypass_register_pack does on UnClick
AI agents use securitypass_register_pack to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
yaml | string | Yes | Pack contents as YAML |
pack_id | string | Yes |
Parameters from the server's own tool schema.
Why securitypass_register_pack is rated Medium
This tool creates or modifies security configuration data (SecurityPack YAML) that is stored for a tenant. While not destructive (reversible via updates), it is a write operation that could affect security posture if misconfigured by an agent. Severity is high because modifying security packs could weaken or alter tenant security policies if an agent makes unintended changes.
From the tool's definition Tool description states 'Save a SecurityPack YAML for the calling tenant', which is a create/modify operation that persists data. The validation against schema indicates structured data storage without deletion.
Attacks that exploit this kind of access
The rule that runs securitypass_register_pack safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For securitypass_register_pack, this is the rule to start with:
securitypass_register_pack stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every securitypass_register_pack call is checked against it from then on.
Questions about securitypass_register_pack
Save a SecurityPack YAML for the calling tenant. Validates against the schema. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
securitypass_register_pack accepts 2 parameters: yaml, pack_id. Required: yaml, pack_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for securitypass_register_pack: 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 UnClick. Nothing to install.
securitypass_register_pack 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 securitypass_register_pack 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 securitypass_register_pack. 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.
securitypass_register_pack is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue