自律タスクを投入する。AIが24/365で自動実行し、完了条件を満たすまでリトライする。 投入する4項目: - why: なぜやるか（背景・目的） - what: どんな体験/行動変容を与えたいか - done: 完了条件（機械検証可能な基準。例:
AI agents invoke task_submit to trigger actions in Wasurenagusa. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool submits autonomous tasks that are automatically and repeatedly executed by an AI agent with no human intervention, triggering external operations and background actions that run indefinitely until a completion condition is met.
From the tool's definition "自律タスクを投入する。AIが24/365で自動実行し、完了条件を満たすまでリトライする。" (Submit autonomous tasks; AI auto-executes 24/365 and retries until completion conditions are met)
Attacks that exploit this kind of access
自律タスクを投入する。AIが24/365で自動実行し、完了条件を満たすまでリトライする。 投入する4項目: - why: なぜやるか（背景・目的） - what: どんな体験/行動変容を与えたいか - done: 完了条件（機械検証可能な基準。例:. It is categorised as a Execute tool in the Wasurenagusa MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Wasurenagusa MCP server in PolicyLayer and add a rule for task_submit: 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.
task_submit is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the task_submit 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 task_submit. 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.
task_submit 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 →