Mark the TODO as incomplete
AI agents use markIncomplete to create or update resources in Remote MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Remote MCP Server environment.
This tool modifies data (changes a TODO's completion status from complete to incomplete) in a reversible manner. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely read data (Read). The operation is a standard write/update that changes application state.
From the tool's definition Tool name 'markIncomplete' and description 'Mark the TODO as incomplete' indicate a state modification operation on an existing TODO item.
Attacks that exploit this kind of access
Mark the TODO as incomplete. It is categorised as a Write tool in the Remote MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Remote MCP Server MCP server in PolicyLayer and add a rule for markIncomplete: 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 Remote MCP Server. Nothing to install.
markIncomplete 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 markIncomplete 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 markIncomplete. 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.
markIncomplete is provided by the Remote MCP Server MCP server (yamanoku-playground/2025-06-03-todo-mcp-server). 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 →