更新任务的信息,支持局部更新
AI agents use update_task to create or update resources in YesDev MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your YesDev MCP Server environment.
An AI agent can call update_task faster than any human can review — one bad instruction and it creates or modifies resources in YesDev MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
更新任务的信息,支持局部更新. It is categorised as a Write tool in the YesDev MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the YesDev MCP Server MCP server in PolicyLayer and add a rule for update_task: 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 YesDev MCP Server. Nothing to install.
update_task 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 update_task 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 update_task. 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.
update_task is provided by the YesDev MCP Server MCP server (yesdevcn/yesdev-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.