Archive a list.
AI agents use archive_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.
Archiving is a data modification that changes the state of a list (from active to archived) without permanently deleting it. This is a write operation rather than destructive because archiving is typically reversible. The medium severity reflects that archiving a list affects task organization and visibility but does not permanently destroy data.
From the tool's definition Tool name 'archive_list' and description 'Archive a list' indicate a state change operation that moves a list to an archived status.
Attacks that exploit this kind of access
Archive a list. 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 archive_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.
archive_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 archive_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 archive_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.
archive_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 →