test_local_extension_compatibility

WHAT IT DOES

What test_local_extension_compatibility does on Todos

AI agents invoke test_local_extension_compatibility to trigger actions in Todos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why test_local_extension_compatibility needs a policy

The tool explicitly runs checks and sandbox dry-runs, which involves executing code or processes locally. Even though it is described as a dry-run (non-destructive), it actively executes operations rather than merely reading or writing data. The blast radius is medium since it runs sandbox tests without installing, limiting but not eliminating potential side effects.

From the tool's definition "Run local CLI/MCP compatibility checks and runner sandbox dry-runs for an extension"

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_local_extension_compatibility Rate-limited

test_local_extension_compatibility stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_local_extension_compatibility": {
      "limits": [
        {
          "counter": "test_local_extension_compatibility_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 test_local_extension_compatibility

What does the test_local_extension_compatibility tool do? +

Run local CLI/MCP compatibility checks and runner sandbox dry-runs for an extension without installing it. It is categorised as a Execute tool in the Todos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_local_extension_compatibility? +

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

test_local_extension_compatibility is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit test_local_extension_compatibility? +

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

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

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