import_onboarding_fixture · Todos MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why import_onboarding_fixture needs a policy

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

Recommended rule Ready

Verdict

import_onboarding_fixture Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "import_onboarding_fixture": {
      "limits": [
        {
          "counter": "import_onboarding_fixture_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Todos, so you can run agents against it safely.

FAQ

Questions about import_onboarding_fixture

What does the import_onboarding_fixture tool do? +

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.

How do I enforce a policy on import_onboarding_fixture? +

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.

What risk level is import_onboarding_fixture? +

import_onboarding_fixture is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit import_onboarding_fixture? +

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.

How do I block import_onboarding_fixture completely? +

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.

What MCP server provides import_onboarding_fixture? +

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.