Set the default list for new tasks.
AI agents use set_default_list to create or update resources in RTM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RTM MCP Server environment.
This tool creates or modifies configuration data (the default list preference) without destroying data or executing arbitrary code. It is reversible—users can change the default list again at any time. The blast radius is minimal since it only affects where future tasks are created by default, not the tasks themselves. This is a Write operation: non-destructive, reversible modification of settings.
From the tool's definition Tool name is 'set_default_list' and description states 'Set the default list for new tasks.' This modifies a user preference/configuration setting, which is a reversible data modification.
Attacks that exploit this kind of access
Set the default list for new tasks. It is categorised as a Write tool in the RTM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RTM MCP Server MCP server in PolicyLayer and add a rule for set_default_list: 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 RTM MCP Server. Nothing to install.
set_default_list 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 set_default_list 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 set_default_list. 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.
set_default_list is provided by the RTM MCP Server MCP server (ljadach/rtm-mcp). 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 →