update_exit_criteria · TasksMultiServer MCP: Risk & Policy

WHAT IT DOES

What update_exit_criteria does on TasksMultiServer

AI agents use update_exit_criteria to create or update resources in TasksMultiServer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TasksMultiServer environment.

WHY IT NEEDS A POLICY

Why update_exit_criteria needs a policy

The tool updates task metadata (exit criteria status) in a reversible manner. It does not delete data, execute external code, trigger financial transactions, or cause irreversible destruction. The blast radius is medium because incorrect updates to task completion criteria could mislead agents about task readiness, affecting workflow decisions, but the changes are auditable and reversible (criteria can be unmarked).

From the tool's definition Tool description states 'Update exit criteria for a task, marking individual criteria as COMPLETE or INCOMPLETE' — this modifies task state data by changing criteria status flags.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_exit_criteria Rate-limited

update_exit_criteria stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_exit_criteria": {
      "limits": [
        {
          "counter": "update_exit_criteria_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches TasksMultiServer, so you can run agents against it safely.

FAQ

Questions about update_exit_criteria

What does the update_exit_criteria tool do? +

Update exit criteria for a task, marking individual criteria as COMPLETE or INCOMPLETE. It is categorised as a Write tool in the TasksMultiServer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_exit_criteria? +

Register the TasksMultiServer MCP server in PolicyLayer and add a rule for update_exit_criteria: 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 TasksMultiServer. Nothing to install.

What risk level is update_exit_criteria? +

update_exit_criteria is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_exit_criteria? +

Yes. Add a rate_limit block to the update_exit_criteria 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.

How do I block update_exit_criteria completely? +

Set action: deny in the PolicyLayer policy for update_exit_criteria. 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.

What MCP server provides update_exit_criteria? +

update_exit_criteria is provided by the TasksMultiServer MCP server (keyurgolani/tasksmultiserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.