Update an existing Task. Pass only the fields you want to change. Commonly used to change status, progress, or dates.
Part of the Mcp Erpnext server.
Free to start. No card required.
AI agents use erpnext_task_update to create or modify resources in Mcp Erpnext. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call erpnext_task_update repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mcp Erpnext.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"erpnext_task_update": {
"limits": [
{
"counter": "erpnext_task_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Mcp Erpnext policy for all 120 tools.
These attack patterns abuse exactly the kind of access erpnext_task_update gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Update an existing Task. Pass only the fields you want to change. Commonly used to change status, progress, or dates.. It is categorised as a Write tool in the Mcp Erpnext MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Erpnext MCP server in PolicyLayer and add a rule for erpnext_task_update: 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 Mcp Erpnext. Nothing to install.
erpnext_task_update 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 erpnext_task_update 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 erpnext_task_update. 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.
erpnext_task_update is provided by the Mcp Erpnext MCP server (@casys/mcp-erpnext). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 120 Mcp Erpnext tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.