import_local_bundle · Todos MCP: Risk & Policy

WHAT IT DOES

What import_local_bundle does on Todos

AI agents use import_local_bundle 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_local_bundle needs a policy

This tool creates or modifies data by importing and merging JSON bundle contents into the local system. It is reversible (data can be updated or reverted), making it a Write operation rather than Destructive. The severity is medium because while it modifies task data, the operation is scoped to local bundles with explicit merge strategies, limiting unintended blast radius compared to arbitrary data modification.

From the tool's definition Tool description states it 'Import[s] a local JSON bundle' which involves loading and integrating external data into the task management system. The mention of 'merge strategy and conflict metadata' indicates the tool modifies existing data structures.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_local_bundle Rate-limited

import_local_bundle 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_local_bundle": {
      "limits": [
        {
          "counter": "import_local_bundle_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_local_bundle

What does the import_local_bundle tool do? +

Import a local JSON bundle with merge strategy and conflict metadata. No cloud calls. 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_local_bundle? +

Register the Todos MCP server in PolicyLayer and add a rule for import_local_bundle: 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_local_bundle? +

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

Can I rate-limit import_local_bundle? +

Yes. Add a rate_limit block to the import_local_bundle 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_local_bundle completely? +

Set action: deny in the PolicyLayer policy for import_local_bundle. 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_local_bundle? +

import_local_bundle 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.