import_onboarding_fixture
Dry-run or apply a bundled local onboarding fixture import. Dry-run is the default.
This record as markdown: /tools/todos/import-onboarding-fixture.md
What import_onboarding_fixture does on Todos
AI agents use import_onboarding_fixture 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.
Why import_onboarding_fixture is rated Medium
This tool creates or modifies task data by importing fixtures. While the dry-run mode mitigates some risk, the apply mode performs reversible data creation/modification (Write category). Severity is medium because fixture imports could overwrite existing tasks or create unwanted task state, but the operation is reversible and limited to local onboarding fixtures (not arbitrary data sources).
From the tool's definition Tool description states 'apply a bundled local onboarding fixture import' — the 'apply' verb indicates data modification/creation. The 'dry-run' default reduces immediate risk but the tool's purpose is to write/import fixture data into the system.
Attacks that exploit this kind of access
The rule that runs import_onboarding_fixture safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For import_onboarding_fixture, this is the rule to start with:
import_onboarding_fixture 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Todos, apply this rule, and every import_onboarding_fixture call is checked against it from then on.
Questions about import_onboarding_fixture
Dry-run or apply a bundled local onboarding fixture import. Dry-run is the default. 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_onboarding_fixture: 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_onboarding_fixture 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_onboarding_fixture 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_onboarding_fixture. 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_onboarding_fixture 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.
More on Todos, and thousands of servers like it.
This server
Across the catalogue