Run comprehensive tests on all Todoist MCP features to verify functionality
AI agents invoke todoist_test_all_features to trigger actions in Mcp Todoist. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a broad suite of tests across all MCP features. 'Comprehensive tests' implies it actively invokes multiple tools including write, delete, and other destructive operations to verify functionality — not merely reading data. The blast radius is high because it could trigger side effects across many Todoist resources (creating, modifying, or deleting tasks, comments, projects, etc.) as part of testing.
From the tool's definition 'Run comprehensive tests on all Todoist MCP features to verify functionality'
Attacks that exploit this kind of access
Run comprehensive tests on all Todoist MCP features to verify functionality. It is categorised as a Execute tool in the Mcp Todoist MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Todoist MCP server in PolicyLayer and add a rule for todoist_test_all_features: 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 Todoist. Nothing to install.
todoist_test_all_features is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the todoist_test_all_features 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 todoist_test_all_features. 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.
todoist_test_all_features is provided by the Mcp Todoist MCP server (@greirson/mcp-todoist). 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 →