プロジェクトの初期設定を行う。自律タスク実行のために、プロジェクトの品質基準・フェーズ・判断基準を登録する。 操作モード: - mode=
AI agents use project_init to create or update resources in Wasurenagusa — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wasurenagusa environment.
This tool initializes a project by registering configuration data (quality standards, phases, decision criteria). This is a Write operation — it creates/stores structured data. While it enables autonomous task execution downstream, the tool itself is setting up configuration, not executing tasks.
From the tool's definition プロジェクトの初期設定を行う。自律タスク実行のために、プロジェクトの品質基準・フェーズ・判断基準を登録する。 (Performs initial project setup. Registers project quality standards, phases, and judgment criteria for autonomous task execution.)
Attacks that exploit this kind of access
プロジェクトの初期設定を行う。自律タスク実行のために、プロジェクトの品質基準・フェーズ・判断基準を登録する。 操作モード: - mode=. It is categorised as a Write tool in the Wasurenagusa MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wasurenagusa MCP server in PolicyLayer and add a rule for project_init: 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 Wasurenagusa. Nothing to install.
project_init 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 project_init 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 project_init. 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.
project_init is provided by the Wasurenagusa MCP server (tsutushi0628/wasurenagusa-mcp). 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 →