AI agents use import_roadmap to create or update resources in Todos — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todos environment.
This tool creates or modifies task roadmap data based on an imported JSON bundle. While it could theoretically be destructive if it overwrites existing roadmaps without safeguards, the description emphasizes 'preview or apply', suggesting deliberate user control. The primary effect is Write (creation/modification of roadmap data) rather than Destructive (irreversible deletion).
From the tool's definition Tool description states 'apply a local roadmap JSON bundle' which indicates modification of task/roadmap data. The verb 'apply' combined with 'roadmap' (a structured collection of tasks/plans) suggests creating or updating task-related data structures.
Attacks that exploit this kind of access
Preview or apply a local roadmap JSON bundle. It is categorised as a Write tool in the Todos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todos MCP server in PolicyLayer and add a rule for import_roadmap: 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 Todos. Nothing to install.
import_roadmap 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 import_roadmap 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 import_roadmap. 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.
import_roadmap is provided by the Todos MCP server (@hasna/todos). 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 →