AI agents use uncomplete_todo to create or update resources in Basecamp MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Basecamp MCP Server environment.
This tool modifies data (a todo's completion status) but does so reversibly—it can be undone by calling complete_todo or uncomplete_todo again. It does not delete data, execute arbitrary code, or cause financial impact. Write is the appropriate category for reversible modifications.
From the tool's definition Tool name 'uncomplete_todo' with description 'Mark a completed todo as incomplete' indicates a state change operation that modifies a todo item by reverting its completion status.
Documented attack patterns abuse exactly the kind of access uncomplete_todo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Basecamp MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for uncomplete_todo:
{
"version": "1",
"default": "deny",
"tools": {
"uncomplete_todo": {
"limits": [
{
"counter": "uncomplete_todo_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}uncomplete_todo 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.
Free to start. No card required.
Mark a completed todo as incomplete. It is categorised as a Write tool in the Basecamp MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Basecamp MCP Server MCP server in PolicyLayer and add a rule for uncomplete_todo: 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 Basecamp MCP Server. Nothing to install.
uncomplete_todo 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 uncomplete_todo 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 uncomplete_todo. 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.
uncomplete_todo is provided by the Basecamp MCP Server MCP server (qusaiisaleem/basecamp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Basecamp MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
56 Basecamp MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.