seopass_register_pack
Register a SEOPass pack from a YAML string. Validates required keys and stores the pack locally for seopass_run.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/seopass-register-pack.md
What seopass_register_pack does on UnClick
AI agents use seopass_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 |
|---|---|---|---|
pack_yaml | string | Yes | Full SEOPass pack definition as a YAML string |
Parameters from the server's own tool schema.
Why seopass_register_pack is rated Medium
The tool writes configuration data (a SEOPass pack) to local storage based on YAML input. This is a reversible modification operation typical of Write category. Severity is medium because misconfigured or malicious packs stored locally could affect downstream seopass_run operations, but the immediate impact is limited to data creation rather than irreversible deletion or code execution.
From the tool's definition Register a SEOPass pack from a YAML string. Validates required keys and stores the pack locally — the tool creates and stores data (write operation).
Attacks that exploit this kind of access
The rule that runs seopass_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 seopass_register_pack, this is the rule to start with:
seopass_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 seopass_register_pack call is checked against it from then on.
Questions about seopass_register_pack
Register a SEOPass pack from a YAML string. Validates required keys and stores the pack locally for seopass_run. 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.
seopass_register_pack accepts 1 parameter: pack_yaml. Required: pack_yaml. 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 seopass_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.
seopass_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 seopass_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 seopass_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.
seopass_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