daily_run
执行每日签到和答题并核验大米。未知题目返回 answer_needed;补充答案时必须同时传入完整题目。resume=true按当前站点日补执行:未到时间或历史已确认完成时离线结束,否则返回attempts中的实际运行;网络/验证失败最多再试一次。不接受历史日期或强制重交参数。
This record as markdown: /tools/1point3acres-toolkit/daily-run.md
What daily_run does on 1point3acres Toolkit
AI agents invoke daily_run to trigger actions in 1point3acres Toolkit. 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.
Why daily_run is rated High
Tool executes automated actions on a third-party website with user credentials, modifying account state.
From the tool's definition 执行每日签到和答题 (execute daily check-in and quiz); 补充答案 (submit answers); 核验大米 (verify rewards)
Attacks that exploit this kind of access
The rule that runs daily_run safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1point3acres Toolkit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For daily_run, this is the rule to start with:
daily_run stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 1point3acres Toolkit, apply this rule, and every daily_run call is checked against it from then on.
Questions about daily_run
执行每日签到和答题并核验大米。未知题目返回 answer_needed;补充答案时必须同时传入完整题目。resume=true按当前站点日补执行:未到时间或历史已确认完成时离线结束,否则返回attempts中的实际运行;网络/验证失败最多再试一次。不接受历史日期或强制重交参数。. It is categorised as a Execute tool in the 1point3acres Toolkit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 1point3acres Toolkit MCP server in PolicyLayer and add a rule for daily_run: 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 1point3acres Toolkit. Nothing to install.
daily_run 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 daily_run 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 daily_run. 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.
daily_run is provided by the 1point3acres Toolkit MCP server (vivian-labs/1point3acres-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1point3acres Toolkit, and thousands of servers like it.
Across the catalogue