AI agents use seevo_register_project to create or update resources in Seevo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Seevo environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | — | プロジェクトのURL（任意） |
target | string | Yes | ターゲットユーザー |
features | array | — | 主な機能のリスト |
tech_stack | array | — | 使用している技術スタック |
description | string | Yes | サービスの説明 |
service_name | string | Yes | サービス名 |
Parameters from the server's own tool schema.
This is a Write operation because it creates new project records in the Seevo system. Severity is high because unauthorized project registration could create persistent entries in an external service, potentially exposing sensitive project details or creating false audit trails.
From the tool's definition Tool description states it 'registers project information to Seevo' (プロジェクト情報をSeevoに登録します), which creates/adds new data in a remote system. The tool requires a token and processes Claude Code analysis results passed as arguments.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
プロジェクト情報をSeevoに登録します。事前にseevo_set_tokenでトークンを設定する必要があります。Claude Codeがプロジェクトを解析した結果を渡してください。. It is categorised as a Write tool in the Seevo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
seevo_register_project accepts 6 parameters: url, target, features, tech_stack, description, service_name. Required: target, description, service_name. The full parameter table on this page comes from the server's own tool schema.
Register the Seevo MCP server in PolicyLayer and add a rule for seevo_register_project: 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 Seevo. Nothing to install.
seevo_register_project 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 seevo_register_project 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 seevo_register_project. 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.
seevo_register_project is provided by the Seevo MCP server (@zelklab/seevo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →